The API beta is live. Sign in at
noxint.ai/dashboard to mint a personal key
and fund data credits; paid REST and MCP calls settle for real. The
discovery surface never needed a key: run
curl https://noxint.ai/api/v1
right now and the contract answers. Launch status is the
ledger of what is on.Authorization
header. That is the entire auth model.
nx_. Pass it as a bearer token. A key never
belongs in a query string.
Key lifecycle
You mint a personal key in the console at /dashboard. The full key is shown once, at creation. Noxint stores only a SHA-256 hash, so it cannot show you the key again or recover a lost one. If a key is exposed, revoke it in the console and mint a new one. Revocation takes effect immediately, not on the next cache flush. You can hold up to 5 active keys per account. Minting a sixth is rejected until you revoke one. Give each tool or agent its own key, so revoking one never disrupts the others.Which operations need a key
The keyless operations teach the contract, so an agent with nothing can
still learn everything. The free keyed operations resolve IDs, list
coverage, and report your credits and rate limit. Only delivered market data
costs data credits. See Data credits for how charges are
counted.
Rate limits
Each personal key gets 60 rate units per minute. Most calls spend one unit. Batch and rank requests spend units equal to their maximum reserved work: aread with 10 IDs spends 10 units, and a rank with limit=50 spends 50,
which is most of a minute’s budget in one call. Size rank.limit to what
you need.
Rate units are a separate meter from data credits, and every attempt spends
units, including rejected calls and free operations. Responses carry public
X-RateLimit-* headers (X-RateLimit-Reset is epoch seconds), and the free
usage operation reports the same window as ISO time alongside your credit
balance.
Personal keys are for your own tooling. Reselling, redistributing,
multi-tenant serving, and serving third parties from your key are
prohibited.
Cache-Control: no-store.