Authentication

All /api/v1 endpoints require a Bearer API key.

curl -sS https://www.agentspapi.com/api/v1 \
  -H "Authorization: Bearer {{API_KEY}}"

Required Header

• Authorization: Bearer <api_key>

Token Format

• rz_live_<key_id>_<secret>

Only Bearer authentication is supported.

Example Requests

cURL

curl -sS https://www.agentspapi.com/api/v1 \
  -H "Authorization: Bearer {{API_KEY}}"

JavaScript (fetch)

const res = await fetch("https://www.agentspapi.com/api/v1", {
  headers: {
    Authorization: `Bearer ${process.env.AGENT_SPAPI_KEY}`,
  },
});
const data = await res.json();

Python (requests)

import os
import requests

resp = requests.get(
    "https://www.agentspapi.com/api/v1",
    headers={"Authorization": f"Bearer {os.environ['AGENT_SPAPI_KEY']}"},
    timeout=30,
)
print(resp.json())

Key Lifecycle

1. Create a named key from /developer/api_keys.
2. Capture the plaintext token immediately. It is shown once and not recoverable later.
3. Store it in your secrets system and reference it via environment variables in runtime.
4. Use the key for one workload or environment so usage and revocation stay isolated.
5. Rotate by creating a replacement key, switching traffic, then revoking the previous key.
6. Review per-key usage in the dashboard to verify expected consumers.

Production Key Handling

• Use a secret manager or deployment secret store for AGENT_SPAPI_KEY.
• Never commit API keys to source control, issue trackers, or chat transcripts.
• Avoid sharing one key across multiple services.
• Revoke keys immediately if exposure is suspected.