API Keys
Create and manage the keys that authenticate your /settle calls.
API keys are the only credential your integration needs. They authenticate POST /settle; every settlement made with a key is attributed to your account and appears in your dashboard.
Creating a key
- Sign in at dashboard.solvador.com with Google or GitHub.
- Open the API Keys tab.
- Create a key and give it a recognizable name.
The full key is displayed exactly once, at creation. After that the dashboard only shows a masked prefix. Store it immediately in your secret manager or environment — if it’s lost, delete the key and create a new one.
Using a key
Pass the key in the X-API-Key header. Only /settle requires it — /verify, /supported, and the discovery endpoints are open. With the x402 SDK, inject it via the createAuthHeaders hook:
const facilitator = new HTTPFacilitatorClient({
url: "https://api.solvador.com",
createAuthHeaders: async () => ({
verify: auth,
settle: auth,
supported: {},
}),
});(Sending the header on /verify too is harmless and keeps the config symmetric.)
Key hygiene
- Keep keys server-side only — never ship one in client or browser code.
- Load keys from environment variables or a secret manager, not from source control.
- Create separate keys for staging and production; you can hold multiple keys per account.
- Rotate by creating a new key, deploying it, then deleting the old one — zero downtime.
The rest of the dashboard
Beyond API keys, the dashboard gives you Overview (settlement activity at a glance), Metrics (settlements and volume over time, broken down by network and asset), Settlements (every settlement attributed to your keys, with network, scheme, payer, amount, and transaction hash), and Plans (quota and billing).