Docs › Authentication

Authentication

How to authenticate requests to the Agent Readiness Platform API.

Authentication: Create an account at /signup to get started. Most read endpoints work without auth. Creating evaluations and accessing your evaluation history requires a JWT Bearer token.

Create an Account

curl -X POST https://agentreadiness.net/api/v1/auth/signup \
  -H "Content-Type: application/json" \
  -d '{"email": "you@company.com", "password": "yourpassword", "name": "Your Name"}'

Returns a JWT token. Include it in subsequent requests:

Authorization: Bearer eyJhbGciOiJIUzI1NiIs...

Log In

curl -X POST https://agentreadiness.net/api/v1/auth/login \
  -H "Content-Type: application/json" \
  -d '{"email": "you@company.com", "password": "yourpassword"}'

Verify Your Token

curl https://agentreadiness.net/api/v1/auth/me \
  -H "Authorization: Bearer YOUR_TOKEN"

API Base URL

All API requests should be made to the following base URL:

https://agentreadiness.net/api/v1

Request Format

The API accepts and returns JSON. Include the following headers on all requests that include a request body:

Header Value Required
Content-Type application/json Yes (for POST/PUT/PATCH)
Accept application/json Optional (default)

Example Request

A complete example request showing all recommended headers:

curl -X POST https://agentreadiness.net/api/v1/quick-eval \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -d '{
    "company_name": "YourProduct",
    "website_url": "https://yourproduct.com",
    "competitors": ["https://competitor1.com"],
    "task": "Set up email sending via API",
    "category": "email_api"
  }'

Example GET Request

GET requests do not require a Content-Type header:

curl https://agentreadiness.net/api/v1/evaluations/{evaluation_id}/status \
  -H "Authorization: Bearer YOUR_TOKEN"

Response Format

All API responses return JSON with appropriate HTTP status codes:

Status Code Meaning
200 Success
201 Created (resource was created successfully)
202 Accepted (async operation started)
400 Bad Request (invalid input)
404 Not Found (resource does not exist)
422 Validation Error (check request body)
500 Internal Server Error

Error Response Format

Error responses include a structured JSON body:

{
  "detail": "Evaluation not found"
}

Rate Limits

Rate limits are applied per-user and per-IP. The current limits are 5 evaluation submissions per hour and 10 auth attempts per 15 minutes.

Authentication is Required

All API endpoints require a valid Bearer token. Get one by signing up at /api/v1/auth/signup and including the token in the Authorization header.

CORS

The API allows cross-origin requests from all origins (*). This means you can call the API from any frontend application, browser extension, or AI agent without CORS issues.

Next Steps