Account infrastructure

Create and verify the credentials, phone numbers, and provider access your account owns. A Pong Client or Account Manager manages only their own resources — omit target flags on writes.

Resource kinds

Resource	Kinds
Transport credential	Exotel, Twilio, Tata
Transport DID	A phone number under one transport credential
Partner credential	Gemini AI Studio (Live models gemini-3.1-flash-live-preview, gemini-3.8-live)
Runtime (Vox server)	Ops-managed; granted to Account Managers

Create and test

Read secret-free metadata first, then create from an absolute private JSON file and test immediately. Tests are read-only checks — they place no calls.

Prompt your AI agent

Recommended

Use the `dino-pong` skill to add a <Gemini AI Studio | Exotel | Twilio | Tata> credential.
Never put the raw key in chat; read it from an absolute private JSON file I name.
Create it, then run its test check and confirm data.status is ok before we rely on it.

Use the Dino CLI directly

dino transport credentials list
dino transport dids list --credential-id <credential-id>
dino partner list

# Create + test a partner (provider) credential, after approval:
dino partner create --input <absolute-private.json> \
  --confirm-mutation partner.create
dino partner test --id <partner-id>

# Create + test a transport credential and a DID:
dino transport credentials create --input <absolute-private.json> \
  --confirm-mutation transport.credentials.create
dino transport dids create --credential-id <credential-id> --input <absolute-private.json> \
  --confirm-mutation transport.dids.create

Require ok: true and data.status: "ok" from each test before you use the resource. Retire only an owned resource, with separate approval for each: partner delete --id, transport credentials delete --id, transport dids delete --credential-id --did-id.

Runtime delegation

Ops creates runtimes and grants them to Account Managers. An Account Manager can delegate a granted runtime to a directly managed Pong Client:

dino runtime test --id <vox-server-id>
dino runtime grant --vox-server-id <id> --client-email <email> \
  --confirm-mutation runtime.voxServer.grant
dino runtime revoke --vox-server-id <id> --client-email <email> \
  --confirm-mutation runtime.voxServer.revoke

Delegation does not transfer ownership or grant DID/partner credentials. A Client process still needs Client-owned DID and partner resources.

Gotchas

• Never put raw credentials in chat, arguments, or skill files. Read them from a private JSON file.
• Creation alone leaves a resource unchecked. Always run its test.
• An Account Manager cannot create or delete a Client's credential.
• Global runtime registration and Ops-to-AM grants belong to Dino Ops.

Next

Use Phone numbers and regions to select a DID for a process.