Developers

Integration reference for MYTOKEN routes, public API, and product boundaries.

Public Site Routes

  • - `/` homepage
  • - `/directory` token listing
  • - `/[slug]` token profile
  • - `/claim` claim flow
  • - `/wallets` developer wallet lookup
  • - `/detector` linked-wallet detector
  • - `/rugged` risk archive
  • - `/help` process documentation
  • - `/pricing`, `/about`, `/contact`, `/privacy`, `/compare`

Public API (v1)

MYTOKEN exposes a small read-only API backed by indexed snapshots. It is not a live passthrough proxy to provider APIs.

  • - `GET /api/v1`
  • - `GET /api/v1/health`
  • - `GET /api/v1/tokens/{slugOrMint}`
  • - `GET /api/v1/wallets/{wallet}`
  • - `GET /api/v1/detector/{mintOrWallet}`
  • - `GET /api/v1/claimed/{token}`

Auth and Quotas

  • - Public access works at lower rate limits.
  • - API keys unlock higher quotas for partner/developer usage.
  • - Provide keys via `x-api-key` or `Authorization: ApiKey <key>`.
  • - Responses include rate-limit headers and `Retry-After` on 429.
  • - Key headers: `X-RateLimit-Limit` and `X-RateLimit-Remaining`.

If you need elevated quotas, contact support through the public contact page.

Semantic Model

  • - Public Research Profile: free token baseline.
  • - Official Links: owner-submitted, paid/claimed layer.
  • - Reference Links: public-source links for research, not owner-verified.
  • - MYTOKEN Intelligence: independent analysis, not owner-controlled.

Current Limits

  • - No OAuth/OIDC public auth surface yet.
  • - No MCP public server surface yet.
  • - No plugin-manifest integrations are published yet.

Machine-Readable Discovery

  • - `/index.md` markdown homepage summary
  • - `/llms.txt` concise agent-facing context
  • - `/llms-full.txt` extended agent-facing context
  • - `/api/openapi.json` API contract
  • - `/sitemap.xml` and `/robots.txt` crawl policy

MYTOKEN emphasizes honest discoverability: only capabilities that exist in production are documented.