SLINGZERO
Launch

Slingzero developers

Public Token Pages, shaped for software and agents.

Search and retrieve public Slingzero Token Pages through a small, versioned, read-only API. The same filtered data is available over REST, MCP, A2A, and an NLWeb-style query endpoint.

Start with the OpenAPI specification

The Slingzero OpenAPI 3.1 document defines every public operation, parameter, response object, and structured error. It includes stable operation IDs suitable for SDK generation and function calling. Public reads require no account, API key, bearer token, or OAuth grant.

curl -s "https://www.slingzero.com/api/v1/token-pages?q=orbit&network=solana&limit=10" \
  -H "Accept: application/json"

Retrieve an exact Token Page

Supply one of the supported mainnet names—solana, ethereum, bsc, polygon, arbitrum, or sui—and the canonical token identifier. URL-encode a full Sui coin type. Hidden, disabled, non-searchable, blacklisted, and missing pages all remain outside the public response surface.

curl -s "https://www.slingzero.com/api/v1/token-pages/{network}/{address}" \
  -H "Accept: application/json"

Errors, caching, and rate limits

Errors are JSON with code, message, hint, docs_url, and a request ID. Correct 400 responses instead of retrying them. Treat 404 as “not public or not found.” Retry a 503 with exponential backoff and honor Retry-After. GET responses advertise cache controls and an advisory public-read rate policy. Contact support before sustained high-volume collection.

Model Context Protocol

Connect a Streamable HTTP MCP client to https://www.slingzero.com/mcp. The product server exposes search_public_token_pages and get_public_token_page, plus an optional interactive ui:// search resource. A separate documentation server at https://www.slingzero.com/mcp/docs keeps product guidance distinct from the data tools. Preview both servers using their published cards.

NLWeb and A2A access

Send a natural-language list query to /ask by GET or POST. Set streaming=true or prefer.streaming=true for server-sent start, result, and complete events. A2A clients can discover the public search skill through the well-known agent card and send JSON-RPC message/send requests to /a2a.

curl -s -X POST "https://www.slingzero.com/ask" \
  -H "Content-Type: application/json" \
  -d '{"query":"community tokens on Solana","mode":"list","streaming":false}'

Authentication and transaction boundary

Current agent surfaces are intentionally public and read-only, so they do not pretend to implement OAuth or issue meaningless credentials. Token creation and management are separate browser workflows that require a person to inspect and sign a wallet transaction. Read auth.md for the complete boundary. Never request a seed phrase or private key.

Data use and trust

Token Page content is supplied by its publisher. Its appearance on Slingzero is not an endorsement, audit, verification, certification, or investment recommendation. Confirm the network and complete address, follow the returned explorer link, and distinguish claims from observed on-chain data. See the Terms, Privacy policy, and Contact page before production use.