401BOT / Developer console

v1 · … uptime over 90 days · … incidents

Calls (30d)

…

Median latency

…

Rate limit

…

Metered spend (30d)

…

API keys

Keys are scoped to one environment and belong to your account. The server stores only a SHA-256 hash, so the plaintext is shown once when it is issued and never again. Rolling a key revokes the previous one immediately.

Secret key live

sk_live_••••••••••••••••

Created: …
Last used: …
Scopes: read:token read:portfolio write:jobs
Allowed origins: Any

Request playground

Build a call and send it. These are real HTTP requests against the live API, with the real status, latency and response body. Open endpoints need no key. The metered /v1/work endpoint runs the agent and needs one.

GET

Ready. Nothing sent yet.

{ }

Endpoints

Base URL https://api.401bot.xyz. Read endpoints marked open need no key at all.

Method	Path	Returns	Tier	Price

Quick start

Webhooks

Portfolio monitoring and long running jobs call you back rather than making you poll. Every delivery is signed with an HMAC over the raw body.

Event	Fires when	Retry
job.completed	A commissioned job is delivered	5 attempts, exponential
job.failed	A job could not be completed and was not billed	5 attempts, exponential
portfolio.drift	A watched portfolio leaves its tolerance band	3 attempts
portfolio.drawdown	A watched portfolio breaches its drawdown floor	3 attempts
settlement.posted	A weekly settlement is written to the ledger	3 attempts

Verify with HMAC-SHA256(raw_body, signing_secret) compared against the X-401-Signature header in constant time.

Errors

Code	Meaning	What to do
400	Malformed request	Check the parameter shape against the endpoint table
401	Missing or invalid key	Reissue above, the old key stops working in 24h
402	Budget ceiling reached	Raise the monthly cap or wait for the reset
404	Unknown identifier	List the collection first to confirm the id
429	Rate limited	Back off using the `Retry-After` header
503	Settlement in progress	Retry once the weekly window closes

Looking for the protocol specification rather than the API surface? That lives in the documentation.