One key, three protocols, and the signal layer behind Z on the other side of it. Ask for a read, subscribe to a stream, or hand the key to an MCP client and let it discover the menu by itself.
READ ONLY
Pick a plan, one payment
GET YOUR KEY
Pick a plan and pay in USDC from your own wallet. The key is minted on the spot and shown once — copy it then. A purchase keeps the plan for 30 days; renew early and the days stack.
BUILDERBuild on the reads.
49 USDC
PRORun a desk, on every lane.
199 USDC
NETWORKRun a trading floor.
500 USDC
FLEETRun a fleet.
1,500 USDC
Three doors, one key
REST
One JSON call per read. GET /v1/skills lists everything your key reaches, with its input contract.
POST /v1/skills/run
MCP
The same reads as native tools. Point any MCP client at the URL, hand it the key, and the menu arrives as a tool list.
POST /v1/mcp
STREAM
Server-sent events. Hold the connection open and take the calls as they land instead of asking again.
GET /v1/stream
What it reads
EARLY
A token named while the call is still new, with who named it.
MATCH
The same token surfacing on two feeds at once — the crossing, not the noise.
RADAR
The live hot list, ranked, with the reading behind each rank.
CALLERS
Who called what, and the record that follows them around.
PROJECTS
One token's whole board — the calls, the traders, the tape.
THE OPEN WEB
Scrape, crawl and map, on the very same key.
The full menu is live, not a list on this page: GET /v1/skills answers with every capability your key reaches and the plan each one needs.
Plans
Plan
USDC / 30 days
Calls / day
Burst / min
Streams
Crawled pages / day
BUILDERBuild on the reads.
49
10,000
120
1
6,000
PRORun a desk, on every lane.
199
50,000
300
5
30,000
NETWORKRun a trading floor.
500
200,000
600
25
120,000
FLEETRun a fleet.
1,500
800,000
2,400
100
480,000
Calling it
Send the key as a bearer token, the same header every endpoint on this site takes. It reads and only reads: it cannot reach a model, sign anything, or post as you.
REST
# what this key can call
curl -H "Authorization: Bearer sk_ansem_..." \
https://api.hansem.io/v1/skills
# one read
curl -X POST -H "Authorization: Bearer sk_ansem_..." \
-H"content-type: application/json" \
-d'{"capability":"network.early","input":{}}' \
https://api.hansem.io/v1/skills/run
The MCP server speaks the 2025-06-18 protocol and publishes one tool per capability, so the client’s own tool list is the menu — nothing to wire up per read.
