Skip to Content
Documentation menu

Get started

Sandbox to production

From signup to live traffic, in order. Dashboard → Monitor → Pilot tracks where you are.

The path

  1. Sign up for the sandbox. No card. You have 30 days in sandbox; after that it stops answering (sandbox_trial_expired) until you activate production.
  2. Create agents and integrate. Follow the quickstart, then the guides that apply to you.
  3. Test for at least 7 days. Production can be activated once your account has 7 days of sandbox testing.
  4. Review security. Trust & security covers the authentication model, encryption, audit design and the shared-responsibility split, for your vendor-risk review.
  5. Activate production. The account owner activates it from the dashboard once the email is verified, billing details are on file and the SLA is accepted. Production has its own agents, keys and records: create them there.
  6. Monitor. Requests for review, Approvers for coverage, Audit log for evidence; Overview, Risk and SLA for the trend.

Go-live checklist

  • Every action that matters calls /v2/authorize first, and the agent has no other way to reach the same system.
  • Your code handles all three decisions. HTTP 200 alone never means go; a missing answer means don't act.
  • Each agent has only the actions and resource scope it needs, and a rate limit you'd be comfortable seeing hit.
  • At least one approver is set up, linked to their login if they'll vote from the dashboard, before any agent can escalate.
  • You've decided which agents (if any) get autonomous authority, and the ceiling for each.
  • Your backend learns review results from a webhook, not by polling in a tight loop.
  • Your highest-risk APIs require a decision token.
  • If agents act for individual people: consent is collected, endUserId is sent, and people can reach their "my agents" page from your app.
  • You store audit.checkpoint events somewhere Authentify can't change.
  • Someone knows where the account kill switch is.

Troubleshooting

SymptomLikely cause
401 Invalid keyAn account key used where an agent key is needed (or the reverse), a revoked key, or a sandbox key against production data.
Every request is deniedCheck reason: account kill switch, billing hold, sandbox trial over, or the agent was revoked after a scope violation.
Action not allowedThe action name isn't in the agent's allowed_actions; names must match exactly.
Scope violationThe resource.id is outside entity_scope. Check the request and the agent's scope before retrying; widen the scope only if it should be wider.
Rate limit exceededThe agent passed its per-minute limit.
Everything escalatesExpected: outside the finance domain’s autonomy, every in-scope request goes to a person. Make sure approvers are set up and use a webhook to learn results.
consent_requiredNo live consent for that endUserId and agent: start a consent session, or check the id matches the one consented.
Amount requiredA rule with an amount limit matched and the request had no context.amount.
Still stuck?

Email support@authentify.bz with the authorizationRequestId; we can see exactly which check decided it.