mxD20 Platform

1. Create a separate key in API Keys with only the permissions the agent needs.
2. Save it in the agent's secure authentication or secrets settings.
3. Give the agent the instructions below or the OpenAPI file.

OpenAPI specification  ·  Agent instructions

The agent must support authenticated HTTP requests. For OpenAI, a custom GPT Action can use the OpenAPI file and Bearer API-key authentication. A native ChatGPT/Work connector uses a separate MCP/OAuth integration; an API key alone does not install a connector. Muse compatibility depends on its available tools.

Create a custom URL

POST https://mxd20.cc/api/create
Authorization: Bearer YOUR_AGENT_KEY
Content-Type: application/json
Idempotency-Key: unique-request-001

{
  "longUrl": "https://example.com/newsletter",
  "customCode": "weekly-drop",
  "mode": "web"
}

Leave out customCode to create a random short URL. Webpage links open the original site; media links serve the file under the short URL.

Safe retries and permissions

Keep the same Idempotency-Key and inputs when retrying one creation request. Use a new value for each new link. An existing custom name returns 409; it is never overwritten.

Read and update permissions apply only to links created by that particular key. Agents cannot change your existing /thedrop link, another key's links, or admin-created links. Replacing a revoked key does not transfer its old links.

GET /api/me checks a key's permissions. GET /api/links lists its links. GET /api/links/{id} reads one; PUT /api/links/{id} updates its destination when permitted. URL-encode returned IDs as path segments.

401: invalid, expired, or revoked key. 403: permission denied. 409: conflict. 429: limit reached; follow Retry-After. Creation quotas reset at 00:00 UTC.