Pricing

Keys and plans

Every request carries a key. A key sits on a plan, and the plan sets how much it may ask for.

Paid in XCH or USDC. A plan is bought and paid on the account page, with an address of its own for every invoice. Prices are computed from running costs.

Plans for sale

What a plan sets

LimitWhat it countsPast it
RateRequests per minute, shown on every answer as x-ratelimit-remaining429 with retry-after
Monthly allowanceRequests this month, shown as x-quota-remaining429 quota_exceeded until the month turns
StreamsOpen WebSocket and server-sent event connectionsThe next connection is refused
Paid untilThe date the subscription runs to401 key_expired

Two kinds of key

Secret key nxs_…

For servers. Sent as Authorization: Bearer <key>, never in a URL and never in a web page.

Publishable key nxp_…

For browsers. Works only from the web origins it was issued for, so it may sit in a page's code; on /ws and /events it may go in the URL as ?key=.

A key that leaks is rotated: the new one works at once and the old one stops at once.

Getting a key

Create an account with a passkey on the account page, make your keys there and buy a plan in XCH. The API reference is open to everyone without a key.