Beta Onboarding

Prepare for IAP beta onboarding

The current beta does not use public self-service signup. Onboarding is operator-driven and works through accounts, linked API keys, and account tokens.

What you will receive

Entitlement API key: authorizes certificate issuance and enforces beta quotas.
Account token: lets you check your usage/status (read-only). It is not the issuance key.

Note: there is no self-service signup during beta — accounts are provisioned manually.

For approved users, beta access currently starts on the free tier at no charge. If you need more capacity, operators can extend quota through a higher plan or add-ons after reviewing the pilot requirements.

What to prepare before requesting access

  • The first agent or workflow you want to certify.
  • The environment where the first beta integration will run.
  • The person responsible for rollout, credentials, and recovery.
  • An estimate of expected continuity volume.

What to send in the onboarding request

A short onboarding request should include the use case, expected number of agents, expected issuance volume, deployment environment, and any timing constraints for the pilot.

Send onboarding requests to admin@ia-protocol.com.

What the operator does next

  • Create your account in the registry.
  • Create a linked API key for entitlement-gated issuance.
  • Create an account token for self-service usage checks.
  • Send you a generated iap-agent setup ... handoff command.

What you do after approval

  • Run the handoff command exactly as sent.
  • Run iap-agent registry check --json.
  • Run iap-agent account usage --json if you received an account token.
  • Complete the first setup using the quickstart guide.

Recommended first rollout

Start with one non-critical agent, create a fresh project-local identity, issue the identity anchor first, then validate one continuity certificate before expanding the rollout.

Plan sizing

Review the built-in plans and current quota model before requesting access.

Read plans and quota

First setup

Once access is approved, use the quickstart to build and verify the first certificate flow.

Open quickstart