Terminal 3 Documentation

Docs

• Get v1did: Get the DID associated with the client
• Post v1didregister: Register a VC issuer
• Get v1openidcauthorize: Validate data and redirect user to the redirect uri
• Get v1openidccredentials: Get list credentials of user by VC issuer or id
• Get v1openidcuser: Get user profile
• Get v1openidcusersocial connections: Get user social connections
• Post v1openidccredentialsproof: Create a credential proof
• Post v1openidctoken: Validate code and generate an access token to user
• Get v2openidcuser: Get user info
• Post v2openidctoken: Validate code and generate an access token to user
• Delete v1sub client: Delete a sub client
• Get v1sub client: Get list of sub clients that belong to the current client
• Get v1sub client 1: Get a detailed sub client
• Post v1sub client: Create a sub client
• Put v1sub client: Update a sub client
• Post v1transactional email template: Create a new client transactional email template
• Post v1transactional email templatesend: Send a transactional email template
• Put v1transactional email template: Update an existing client transactional email template
• Get v1user social data: Get user social data for client
• Get v1user wallet addresses: Get wallet addresses of an user
• Post v1usercreate: Create a user for client
• Get v1vcissuercredentials: Get list of credentials by id or holder DID
• Post v1vcissuercredentialsproof: Generate credential proof from VCs
• Post v1vcissuerstore: Store a VC generated by user
• Changelog: What's changed in these docs, and what we know about SDK version history so far.
• Claim Your API Key & credits: Claim your account, key, and test credits in one step — self-serve, no approval.
• Set Up Development Environment: Two more steps to get ready for writing your first TEE contract.
• Quickstart: Get your first authenticated call to Terminal 3 working in under 10 minutes.
• 2. Build your TEE contract
• 4. Invoke your TEE contract
• 3. Register your TEE contract
• 5. Test your TEE contract
• 1. Write your TEE contract
• What is z-namespace?
• ADK Tour: The shape of the ADK in five pieces, before you write any code.
• Agent Auth: How an AI agent authenticates to T3N, and how it gets permission to act on a contract.
• What is T3 Agent Developer Kit (ADK)?: An SDK suite that allows developers to build safe and secure AI agents
• Why T3 ADK?: Give AI agents real-world capabilities without compromising user privacy, security and compliance
• SDK & API Reference: Every confirmed ADK method, WIT host interface, and API surface in one place.
• Using AI Coding Assistants: A ready-to-use skill file that teaches Claude Code, Codex, Cursor, and other AI coding tools how to build with the T3N ADK.
• Dev Community Support: This section provides the various channels for developer community support from Terminal 3.
• Capabilities come from your WIT imports: Capabilities are determined by the host interfaces imported in your contract's world.wit
• Common errors
• Create Tenant KV Maps
• Outbound HTTP calls are authorized by the user, not the contract
• Placeholders in outbound calls: Send private data to a third-party API without it ever entering your contract, using http-with-placeholders.
• Seed API key into secrets map: Seed the API key into the secrets map using the map-entry-set control call.
• Payroll Agent
• About
• Decentralized ID (DID): Decentralized Identities and their methods
• Smart VCs: Verifiable Credentials
• Platform Overview
• Delegate Access: How to grant and manage access permissions for your data.
• Architecture: A compliance-aware, multi-region, private-first architecture
• Data Encryption: Private data is always encrypted in transit and at rest
• Decentralized Identifiers (DIDs): Universal ID for both human and agent
• Host API: Host API grants TEE contracts controlled access to system capabilities
• Trusted Execution Environment (TEE) Node: Confidential, programmable, and verifiable computation
• Tokens: How T3N tokens meter TEE contract execution and storage
• Storage Namespaces: Tenant-owned TEE contracts and data are named in z-namespace
• What is the T3 Network (T3N)?: A decentralized confidential computing network
• Why T3N?: Regain trust, privacy, and accountability in the age of AI
• Delegate Access to AI Agents: How T3N allows you to delegate access to AI agents
• Delegate Access to Human Helpers: How T3N allows you to delegate access to human helpers
• Confidential Multi-Party Computation: How T3N enables confidential multiparty computation (MPC)
• Reusable Verified User Data: How T3N allows you to reuse verified user data

OpenAPI Specs

• terminal-3-openapi
• openapi

Optional

• terminal3.io
• Developer TG