Discovery and account

An agent with no key and no credits can learn this entire API from the API itself. Five operations cost zero data credits: docs, schema, resolve, coverage, and usage. The first two need no key at all; the other three authenticate with a personal key but still cost nothing.

docs

Returns the contract guide as markdown, written for both humans and agents. The section parameter defaults to index; values are index, quickstart, domains, access, grammar, refusals, resolve, errors, pricing, examples, and changelog. The response is raw markdown with no JSON envelope, and most sections run a few hundred tokens: sized for a context window, not a browser.

curl 'https://noxint.ai/api/v1/docs?section=grammar'

schema

Returns one operation’s machine contract: parameters, defaults, enums, and error set as structured JSON. Keyless. The optional resource parameter names one of the 23 operations; omit it to get the index.

curl 'https://noxint.ai/api/v1/schema?resource=funding'

docs plus schema is a complete self-teaching loop. Point an agent at the base URL and it can bootstrap the whole surface.

resolve

Turns a human query into canonical asset IDs with ranked evidence. Requires a key, costs nothing. Captured live on 2026-07-16:

{
  "data": {
    "query": "bitcoin",
    "best": {
      "asset_id": "crypto:bitcoin",
      "symbol": "BTC",
      "confidence": 0.95
    },
    "coverage": { "returned": 6, "omitted": 49, "exhaustive": false }
  }
}

bitcoin resolves to Bitcoin, decisively, with the confidence stated. Ticker squatters on major names are disclosed as warnings in the payload instead of promoted into the answer. And when a query is genuinely ambiguous (apple matches Apple Inc., an OTC filer, and two Solana tokens), best is null and the ranked matches carry warnings like symbol_collides_with_covered_equity. Ambiguity is surfaced, never silently resolved wrong.

string

required

The search query. 1 to 80 characters.

integer

default:"10"

Maximum matches to return per plane. 1 to 25.

string

Narrows results to one network, which matters for clone-heavy tickers.

coverage

Lists the assets Noxint knows, or inspects one asset in detail. Requires a key, costs nothing. To browse, filter by plane (crypto or equity), tier (for crypto: core, listed_token, or contract_token), alive, cursor, and limit (default 100, up to 500). To inspect instead, pass id alone: the response returns a covered verdict for every operation with a typed reason where the answer is no, plus history depth per interval. Real numbers and worked examples are on the coverage page.

curl -H 'Authorization: Bearer nx_your_key' \
  'https://noxint.ai/api/v1/coverage?plane=crypto&tier=core&limit=500'

usage

Reports your remaining data credits and your rate-limit window. Takes no parameters, costs nothing. Captured live, 2026-07-16:

{
  "data": {
    "credits_remaining": 494,
    "rate_limit": { "limit": 60, "remaining": 59, "reset_at": "2026-07-16T09:44:00.801Z" }
  }
}

Because MCP cannot re-poll with a conditional header, usage is how an agent checks its own balance between calls.

All five operations cost zero data credits. They still spend a rate unit, so they count against the 60-rate-unit-per-minute personal-key limit.

Using the API

Guides

Operations

MCP

Discovery and account

docs

schema

resolve

coverage

usage

​docs

​schema

​resolve

​coverage

​usage

docs

schema

resolve

coverage

usage