GET/v1/keys/verify

Public. No key, and no quota deducted.

What it does

Links carry the token in the fragment (#t=), which never reaches this server; the page's script reads it. Links sent before carry ?token= and land on the same page. With Accept: application/json (an agent relaying a link) the answer is the same facts as POST /v1/keys/verify/details, and nothing is consumed either.

Call it

bash

curl -fsS -X GET "https://api.mapmap.ai/v1/keys/verify"

Parameters

Name	In	Required	Description
token	query	no	Token of a link sent before the fragment form; current links carry it as `#t=`, which the page reads

Responses

200The confirmation page (HTML), or with Accept: application/json and a token the request facts. Nothing is confirmed or consumed

Field	Type	Required	Description
kind	string	yes	`"new-signup"` when nobody has verified the address yet (the welcome mail), `"new-key-on-account"` when the address already has a verified key (the owner notice).
request	KeyRequestView	yes	What the request said about itself, when and roughly where.
state	string	yes	The key's state: `provisional` until confirmed, `verified` once it is.

400JSON only: missing, unknown, used or expired token

Error bodies follow the shared problem model documented on API conventions.

Also under self-serve

GET /v1/jobs GET /v1/jobs/{id}POST /v1/keys DELETE /v1/keys/self GET /v1/keys/self POST /v1/keys/self/email POST /v1/keys/self/email/verify POST /v1/keys/self/webhook-secret POST /v1/keys/verify POST /v1/keys/verify/deny POST /v1/keys/verify/details GET /v1/usage POST /v1/x402/topup

Generated from https://api.mapmap.ai/openapi.json on 2026-11-01 · operationId verify_page