Authentication

API keys

LLM Prover uses named API keys for programmatic access. Keys are created in the Developer section of your dashboard under the Keys tab.

Each key is:

• Named – give it a meaningful label (e.g. “CI pipeline”, “Local dev”)
• Independently revocable – revoking one key does not affect others
• Scoped to your account – all keys have the same access as your account tier

The raw key is shown exactly once when created. Copy it immediately – it cannot be retrieved again. If you lose it, revoke it and create a new one.

Passing your key

Include your key in the Authorization header on every request:

curl https://api.llmprover.pysolvr.com/models \
  -H "Authorization: llmprover_a1b2c3d4_e5f6g7h8i9j0k1l2m3n4o5p6"

Keys follow the format llmprover_{8 chars}_{24 chars}. The llmprover_ prefix identifies the key as an LLM Prover developer key.

Key limits by tier

Key expiry

Pro and above can set an expiry when creating a key (30, 90, 180, or 365 days). Starter keys do not expire.

Expired keys are rejected with a 401. Create a new key before the old one expires if you need continuity.

Security

• Never commit keys to source control. Use environment variables or a secrets manager.
• Rotate keys periodically. Revoke any key you suspect has been exposed.
• Use one key per integration – this makes it easy to revoke a single integration without affecting others.
• Keys are tied to your account tier. If your plan changes, key access changes with it.

Revoking a key

Go to Developer > Keys in the dashboard. Click Revoke next to the key. Revocation is immediate – any in-flight requests using that key will fail.

Revoked keys are retained in the audit log but cannot be re-activated. Create a new key to replace it.

What’s next

• Rate limits – per-tier limits and how to handle 429s
• Errors – error codes and response shapes