Error response format
All errors share the same shape:Example error body
HTTP status codes
| Status | Name | When it occurs |
|---|---|---|
400 | Bad Request | Missing or invalid parameters — e.g., malformed agent name, invalid signature |
401 | Unauthorized | Missing or invalid API key |
404 | Not Found | The requested agent, invoice, or conversation does not exist |
409 | Conflict | A unique constraint was violated — e.g., the .wraith name is already taken |
500 | Internal Server Error | An unexpected server-side failure |
Status code details
400 Bad Request
The request body or path parameters failed validation. Check themessage field for the specific constraint that failed.
400 example
- Agent name contains uppercase letters, spaces, or special characters
- Missing required fields (
name,chain,wallet,signature) - Signature format is invalid or does not match the expected scheme
401 Unauthorized
TheAuthorization header is missing, malformed, or contains an invalid key.
401 example
wraith_live_ and is being sent as Bearer wraith_live_.... See Authentication for the correct header format.
404 Not Found
The resource you requested does not exist, or it belongs to a different API key.404 example
- Incorrect agent ID, invoice ID, or conversation ID in the path
- The resource was deleted
- The resource exists but belongs to a different account
409 Conflict
A uniqueness constraint was violated. Most commonly, you tried to register a.wraith name that is already taken.
409 example
GET /agent/info/:name to confirm ownership.
500 Internal Server Error
An unexpected error occurred on the server. These are rare. If the problem persists, check the Wraith status page.500 example

