Documentation
Authentication
urls.bid uses X (Twitter) OAuth for user authentication and API keys for programmatic access. To authenticate API requests, include your API key in the Authorization header.
Links API
Create a new short link. Optionally make it a gated (paid) link by providing a price.
Retrieve a list of all your created links.
Get metadata details for a specific link by its slug (public GET endpoint).
Update a link's destination URL or price.
Delete a link permanently.
Get click analytics and revenue data for a link.
Create a promotional link with special tracking.
Bio API
Create your bio profile.
Get your own bio profile details.
Get a public bio profile.
Add a new link to your bio profile.
Update a bio link.
Remove a link from your bio.
Reorder the links on your bio profile.
x402 Endpoints
These endpoints support the x402 micropayment protocol for agentic monetization.
Resolve a short link. Returns 402 Payment Required if the link is gated.
Access a gated file.
Query a gated dataset.
Agent-specific API routes with built-in x402 support.
Well-known Endpoints
Standardized endpoints for agent discovery and protocol support.
| Path | Description |
|---|---|
| /.well-known/agent.json | Agent capability discovery manifest |
| /.well-known/x402.json | x402 payment protocol configuration |
| /llms.txt | Context file for LLMs and AI agents |
Error Codes
| Code | Status | Description |
|---|---|---|
| 400 | Bad Request | Invalid parameters provided |
| 401 | Unauthorized | Missing or invalid API key |
| 402 | Payment Required | x402 payment required to access resource |
| 404 | Not Found | Resource does not exist |
| 429 | Too Many Requests | Rate limit exceeded |
Rate Limits
API requests are limited to 100 requests per minute per IP address, and 1000 requests per hour per API key. If you exceed these limits, you will receive a 429 Too Many Requests response.