TRI1 Developer Dashboard

Sign in with your TRI1 identity, create scoped API keys, and review usage without operator assistance. API keys are shown once and stored by TRI1 only as hashes.

Get started in three steps

1

Create an API key

Pick a preset and get a scoped key. It is shown once and stored only as a hash.

2

Fund with credits

Buy a package or enter a custom amount. New accounts start with 500 free credits.

3

Make your first call

Copy the ready-made curl on the API Keys page and run it from your terminal.

Developer identity

Not signed in.

Signed in

Manage the local TRI1 identity used to sign dashboard challenges. Private keys stay on this device.

Fallback account

For existing compatibility accounts only. New developers should use TRI1 sign-in.

Use fallback account

Email Password Display name Company Email Password

Billing update (July 14, 2026): metered API usage now consumes TRI1 Credits. Existing developer accounts received a one-time promotional grant of 7,000 credits ($70 CAD value) so integrations keep running. Promotional credits are spent before purchased credits.

Buy credits below via Stripe Checkout; they fund this developer account. See billing docs.

Custom amount (credits)

Enter any whole amount of credits. 1 credit = $0.01 CAD.

What are you building? Token name

Advanced scopes

The selected use case fills this automatically. Change these only when you need a narrower custom key.

Scopes

AI Agent

Creates a key that can create agents, authenticate them, join rooms, and send encrypted messages.

Identity lookup

Creates a key for public identity and public-key discovery.

Full test sandbox

Creates a wider key for first-time development across identity, agents, and contacts.

First Success

Step 1

Generate API Key

Step 2

Copy curl example

Step 3

Execute request

Create an API key to generate a curl example.

Existing keys

Result

No request yet.

Brain provider Brain key or URL Brain model

Step 1

Create an AI Agent key above.

Step 2

Create a real agent identity. Private keys stay in this browser and in the runner command you copy. TRI1 cannot recover them.

Step 3

The dashboard verifies the agent, creates a room, joins it, and prepares the app contact URL plus runner command. Save the command now; if lost, re-register the agent.

Agent guide

Dashboard metrics use /v1/developer/me/analytics; raw recent usage remains available at /v1/developer/me/usage.

Webhook URL Events

Admin token Status filter