HostThe API: the engine, without the app in front of it
Everything the app does is reachable as an endpoint — the keyless free scanner, graded /v1 reads, x402 metered calls, and the embeds and badges that put the scan inside other products.
The public API is the same machinery the app surfaces, minus the app: token risk reads, market data and the trading surfaces, exposed as HTTP endpoints that anything can call. The docs at /docs/api/ spell out every route with its parameters and response shape — this page is the map, the docs are the reference.
The free lane: the scanner, keyless
The headline endpoint is the one this site's own pages call: a same-origin POST to the scanner with a token address, returning the graded risk read — authorities, holders, liquidity, sell simulation — with no key and no signup. It exists so that "check the token first" is a thing any tool can do for free, which is the entire point of a safety product having an API.
The graded and metered lanes
Above the free lane sit the graded /v1 endpoints for heavier reads, and the x402 surface — machine-payable calls priced per request, advertised in the discovery manifest at the well-known path. The embed lane rounds it out: badges and widgets that render the scan verdict inside other sites, and the badge builder on the integrate page that generates them.
| Lane | Auth | What it's for |
|---|---|---|
| Scanner | None — keyless POST | The graded token risk read: authorities, holders, liquidity, sell simulation |
| /v1 graded | API key | Heavier reads and higher volume than the free lane carries |
| x402 | Machine payment per call | Agents and services paying per request — no account, no key |
| Embeds & badges | None | The scan verdict rendered inside your own product or page |
What a scan response actually returns
The risk read is graded, not a bare boolean: a risk level over the checks the engine runs — mint and freeze authority state, holder concentration, liquidity depth, a sell-side simulation for honeypots on Solana, and contract-flag reads (hidden mints, proxies, blacklist functions) on the EVM chains. The same fields the app's own scanner card renders, returned as JSON — how to read a risk scan decodes each one.
Fair-use in one line: the free scanner is for reading tokens, not for building a competing index of the whole chain. Metered lanes exist for volume; the free lane stays free because safety reads shouldn't have a toll booth.
Build on the same engine
Keyless scanning for free, graded endpoints for volume, x402 for machine-paying callers — the docs list every route.
Frequently asked
Is the NexFlow API free?
The scanner is — a keyless POST with a token address returns the graded risk read. Heavier /v1 endpoints and the x402 machine-payable surface cover volume use.
Where are the API docs?
At nexflowscan.com/docs/api/ — every route with its parameters and response shape, including the scanner, the graded endpoints, x402 and the embed lanes.
What is x402 on NexFlow?
The machine-payable lane: endpoints priced per request, advertised in the well-known discovery manifest so agents can find and pay for calls without a signup.
Can I embed the scan result on my own site?
Yes — the badge and embed lane renders the scan verdict inside other products, and the integrate page's badge builder generates them.
Is there a rate limit on the free scanner?
A fair-use cap of about a hundred checks per day per address — enough for any tool that checks tokens before showing them. The metered lanes exist for volume beyond that.