OnlyDoge Developer Resources
OnlyDoge Platform API documentation, OpenAPI specifications, authentication, error format, rate limits, versioning and agent integration guidance.
OnlyDoge Platform API
The OnlyDoge Platform API provides Dogecoin explorer and analytics reads at https://platform.onlydoge.io. Use the live API reference and OpenAPI 3.1 specification for exact paths, parameters, limits and response schemas. The specification is maintained by the Platform; the links below point to its authoritative version.
Authentication
Protected /v1 endpoints require an API token in the x-api-token request header. Ask your Platform administrator to provision access. POST /v1/keys/ requires an admin key once the initial key exists; it is not an open production signup endpoint. Tokens are returned once when created. Keep them on your server, never in browser code, public URLs or committed files.
For an authorized read, send GET https://platform.onlydoge.io/v1/explorer/blocks?limit=1 with x-api-token: YOUR_API_TOKEN and Accept: application/json. Replace the placeholder only in your private runtime. Follow the live specification for pagination, validation errors and other explorer endpoints. This documentation does not create an API key or change permissions.
Website API and error format
This website publishes its own HTTP surface separately from the Platform API. The OpenAPI 3.1 document at https://www.onlydoge.io/openapi.json describes every public resource served from www.onlydoge.io: the Markdown documentation, llms.txt, the sitemap and the browser chat transport at POST /api/v1/chat. Every operation in that document declares typed response schemas. The chat transport is protected by bot verification and exists for the OnlyDoge web client; it is not a general-purpose agent API. Structured Dogecoin records come from the authenticated Platform API described above.
Errors from /api paths, method mismatches, unsupported representations and unknown /api URLs use RFC 9457 Problem Details with the application/problem+json media type. Each problem carries the standard type, title, status, detail and instance members plus two extension members: code, a stable machine-readable identifier to branch on, and hint, resolution guidance. The problem types are listed below; each type URI dereferences to its entry on this page. Unknown paths outside /api return HTTP 404 with a Markdown body for non-browser clients and the HTML not-found page for browsers; both link to the sitemap and llms.txt.
Chat responses include the IETF RateLimit and RateLimit-Policy header fields (policy "chat": 10 requests per 60 seconds per client), the earlier-draft RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset fields, and Retry-After on a 429 response. Read the remaining quota from these headers before retrying instead of probing for failures. Unsupported methods on API paths return 405 with an Allow header.
- not_found (HTTP 404)
- Not Found. No resource exists at the requested URL. Check the URL against the sitemap at https://www.onlydoge.io/sitemap.xml, start from https://www.onlydoge.io/llms.txt for Markdown documentation, or read https://www.onlydoge.io/developers for the API surface. Explorer views use /blocks, /blocks/{height-or-hash}, /tx/{txid}, /address/{address} and /mempool.
- method_not_allowed (HTTP 405)
- Method Not Allowed. The resource exists but does not support the request method. Retry with one of the methods listed in the Allow response header.
- not_acceptable (HTTP 406)
- Not Acceptable. None of the representations requested in the Accept header are available for this resource. Interactive explorer pages are text/html only. The homepage and information pages also serve text/markdown; https://www.onlydoge.io/llms.txt lists every Markdown resource.
- invalid_request (HTTP 400)
- Invalid Request. The request body or parameters were not valid. Send a JSON body with a non-empty "messages" array whose entries have a "role" of "user" or "assistant" and text content, as described in the OpenAPI document at /openapi.json.
- access_denied (HTTP 403)
- Access Denied. The request was not accepted as a verified browser session. The chat transport serves the OnlyDoge browser client and is protected by bot verification. Programmatic access to Dogecoin records uses the OnlyDoge Platform API with a provisioned token; see https://www.onlydoge.io/developers.
- rate_limited (HTTP 429)
- Too Many Requests. The request quota for this resource has been used. Wait for the number of seconds given in the Retry-After header before retrying. The RateLimit and RateLimit-Policy headers describe the remaining quota and the policy window.
Versioning and deprecation
Website API paths are versioned in the URL: the current chat transport is /api/v1/chat. Changes that add fields, headers or resources are not breaking and do not change the version. A breaking change ships under a new path prefix while the previous version keeps working through a deprecation period of at least 90 days.
A deprecated resource announces its status on every response with the RFC 9745 Deprecation header (the date it was deprecated as a Structured Field Date), the RFC 8594 Sunset header (the HTTP-date after which it may stop responding) and Link headers with rel="deprecation", rel="sunset" and rel="successor-version". Agents should treat a Deprecation header as a signal to migrate before the Sunset date. The Platform API versions its paths under /v1; consult its live reference for the current Platform contract. Current website deprecations are listed below.
- /api/chat (alias of /api/v1/chat)
- Deprecated on 2026-09-07 with a sunset of 2027-01-01. Every response from the alias carries Deprecation, Sunset and Link headers. Move to /api/v1/chat; the request and response contract is identical.
Agents and supported integrations
Use the website for public explorer views and the authenticated Platform API for structured records. The website's /api/v1/chat endpoint is the protected browser chat transport, not a public agent API. OnlyDoge does not currently publish an MCP server or a command-line tool; the Platform API, this documentation and the Markdown resources are the supported integration points. Discover agent guidance at /llms.txt, and request these documentation pages with Accept: text/markdown or use their .md links.