Terminal 3

Terminal 3 (T3) is a data-freedom and decentralized-identity company (founded 2023, Hong Kong) building privacy-preserving identity, verifiable credentials, and confidential computing infrastructure. Its products include T3 Verify (enterprise KYC/AML with real-time identity and liveness verification across 190+ countries and reusable verifiable credentials), T3 Identity (full-stack digital identity with passwordless auth, OpenID Connect SSO, decentralized identifiers, and verifiable credentials), Agent Command (secure, cryptographically verifiable AI-agent identity, permissions, and audit), and the T3 Network (T3N) — a hardware-secured confidential-computing network running tenant TEE contracts inside Intel TDX enclaves. Terminal 3 publishes a REST API (DID, OpenID Connect, verifiable credentials, sub-clients, transactional email, and user data) and an Agent Developer Kit (ADK) with a first-party TypeScript SDK family. Backed by 500 Global, ConsenSys Mesh, CMCC Global, Bixin Ventures, and Cherubic Ventures.

Terminal 3 publishes 7 API contracts indexed on the APIs.io network, including DID V1 API, OpenID Connect V1 API, OpenID Connect V2 API, and 4 more. Tagged areas include Company, Identity, Decentralized Identity, Verifiable Credentials, and OpenID Connect.

The Terminal 3 catalog on APIs.io includes 1 Spectral governance ruleset.

Terminal 3’s developer surface includes authentication, changelog, sandbox, documentation, getting-started guide, support, engineering blog, and 25 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

44.2/100 developing ▬ flat Agent 21/100 agent aware Front door AI 6/6 dominant Heartbeat 44/100 going silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 4 Agent Skills

Company Identity Decentralized Identity Verifiable Credentials OpenID Connect KYC AML Confidential Computing AI Agents Privacy Web3 DID

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 44.2/100 · developing

Contract Quality 2.5 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 7.5 / 15

Operational Transparency 4.4 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 5.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/terminal-3/"><img src="https://apis.io/badge/terminal-3/card.svg" alt="Terminal 3 on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 13.3 — up to +21.7 composite points
Access Clarity scores 50.0 — up to +10.0 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/terminal-3/apis.yml: open an issue on github.com/api-evangelist/terminal-3 to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
OpenID Certified Implementations (OIDC, FAPI, OpenID4VC)	standard	26.8 (thin)	-	1
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	26.8 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Defense In Depth

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenID Connect

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 7

Individual APIs this provider publishes, each with its own machine-readable definition.

Terminal 3 DID V1 API

Decentralized identifier (DID) operations.

Terminal 3 OpenID Connect V1 API

OpenID Connect authorization, token, userinfo, and credential operations (v1).

Terminal 3 OpenID Connect V2 API

OpenID Connect token and userinfo operations (v2).

Terminal 3 Sub Client V1 API

Manage sub-clients under a Terminal 3 tenant.

Terminal 3 Transactional Email Template V1 API

Create, update, and send transactional email templates.

Terminal 3 User V1 API

User creation and user data (social data, wallet addresses).

Terminal 3 VC V1 API

Verifiable Credential issuer operations.

Scroll for all 7

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Terminal 3 DID V1 API

OPEN COLLECTION

Terminal 3 DID V1 OpenID Connect V1 API

OPEN COLLECTION

Terminal 3 DID V1 OpenID Connect V2 API

OPEN COLLECTION

Terminal 3 DID V1 Sub Client V1 API

OPEN COLLECTION

Terminal 3 DID V1 Transactional Email Template V1 API

OPEN COLLECTION

Terminal 3 DID V1 User V1 API

OPEN COLLECTION

Terminal 3 DID V1 VC V1 API

OPEN COLLECTION

Scroll for all 7

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Issue and store a verifiable credential

AGENT SKILL

Onboard a user and read their identity data

AGENT SKILL

Authenticate a user with OpenID Connect

AGENT SKILL

t3n-adk-quickstart

AGENT SKILL

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Terminal 3

SLA

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Terminal 3 API Rules

40 rules · 38 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Terminal 3 Openapi Overlay

2 actions · update · terminal-3-openapi.yml

DERIVED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Terminal 3 Authentication

http/apiKey · 2 schemes

SECURITY

Terminal 3 Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Terminal 3 Vulnerability Disclosure

contact published

SECURITY

Terminal 3 Trust Center

SOC 2, SOC 2 Type 1, ISO 27001

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Terminal 3 Agentic Access

24 operations · 13 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

Sandbox

DeveloperPortal

GettingStarted

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

Packages

Packages

SDKs

SDKs

GitHubOrganization

GitHubOrganization

Access & Security 6

Authentication, authorization, and security posture

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Compliance

DomainSecurity

Authentication

Operate 3

Status, limits, changes, and where to get help

StatusPage

StatusPage

ChangeLog

ChangeLog

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Blog

Blog

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: terminal-3
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/terminal-3.png
name: Terminal 3
description: Terminal 3 (T3) is a data-freedom and decentralized-identity company (founded 2023, Hong Kong) building privacy-preserving
  identity, verifiable credentials, and confidential computing infrastructure. Its products include T3 Verify (enterprise
  KYC/AML with real-time identity and liveness verification across 190+ countries and reusable verifiable credentials), T3
  Identity (full-stack digital identity with passwordless auth, OpenID Connect SSO, decentralized identifiers, and verifiable
  credentials), Agent Command (secure, cryptographically verifiable AI-agent identity, permissions, and audit), and the T3
  Network (T3N) — a hardware-secured confidential-computing network running tenant TEE contracts inside Intel TDX enclaves.
  Terminal 3 publishes a REST API (DID, OpenID Connect, verifiable credentials, sub-clients, transactional email, and user
  data) and an Agent Developer Kit (ADK) with a first-party TypeScript SDK family. Backed by 500 Global, ConsenSys Mesh, CMCC
  Global, Bixin Ventures, and Cherubic Ventures.
url: https://raw.githubusercontent.com/api-evangelist/terminal-3/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: profiled
x-tier-reason: enriched-from-portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
x-docs-hosting: vercel
tags:
- Company
- Identity
- Decentralized Identity
- Verifiable Credentials
- OpenID Connect
- KYC
- AML
- Confidential Computing
- AI Agents
- Privacy
- Web3
- DID
apis:
- aid: terminal-3:terminal-3-did-v1-api
  name: Terminal 3 DID V1 API
  description: Decentralized identifier (DID) operations.
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - DID V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-did-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-openid-connect-v1-api
  name: Terminal 3 OpenID Connect V1 API
  description: OpenID Connect authorization, token, userinfo, and credential operations (v1).
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - OpenID Connect V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-openid-connect-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-openid-connect-v2-api
  name: Terminal 3 OpenID Connect V2 API
  description: OpenID Connect token and userinfo operations (v2).
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - OpenID Connect V2
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-openid-connect-v2-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-sub-client-v1-api
  name: Terminal 3 Sub Client V1 API
  description: Manage sub-clients under a Terminal 3 tenant.
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - Sub Client V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-sub-client-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-transactional-email-template-v1-api
  name: Terminal 3 Transactional Email Template V1 API
  description: Create, update, and send transactional email templates.
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - Transactional Email Template V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-transactional-email-template-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-user-v1-api
  name: Terminal 3 User V1 API
  description: User creation and user data (social data, wallet addresses).
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - User V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-user-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
- aid: terminal-3:terminal-3-vc-v1-api
  name: Terminal 3 VC V1 API
  description: Verifiable Credential issuer operations.
  humanURL: https://docs.terminal3.io/developers/adk/reference
  baseURL: https://staging.terminal3.io
  tags:
  - VC V1
  properties:
  - type: OpenAPI
    url: openapi/terminal-3-vc-v1-api-openapi.yml
  - type: APIReference
    url: https://docs.terminal3.io/api-reference/t3-api/getting-started
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://blog.terminal3.io/rss/
  type: BlogRSS
- type: Overlay
  url: overlays/terminal-3-openapi-overlay.yaml
- type: AgenticAccess
  url: agentic-access/terminal-3-agentic-access.yml
- type: TrustCenter
  url: security/terminal-3-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/terminal-3-vulnerability-disclosure.yml
- type: Security
  url: https://terminal3.io/security
- type: Compliance
  url: https://terminal3.io/security
- type: DomainSecurity
  url: security/terminal-3-domain-security.yml
- type: Authentication
  url: authentication/terminal-3-authentication.yml
- type: Packages
  url: packages/terminal-3-packages.yml
- type: SDKs
  url: packages/terminal-3-packages.yml
- type: X-MCPServerCandidate
  url: mcp/terminal-3-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/terminal-3-llms.txt
- type: Conformance
  url: conformance/terminal-3-conformance.yml
- type: ErrorCatalog
  url: errors/terminal-3-problem-types.yml
- type: Lifecycle
  url: lifecycle/terminal-3-lifecycle.yml
- type: StatusPage
  url: https://status.terminal3.io
- type: Conventions
  url: conventions/terminal-3-conventions.yml
- type: ChangeLog
  url: changelog/terminal-3-changelog.yml
- type: Sandbox
  url: sandbox/terminal-3-sandbox.yml
- type: DataModel
  url: data-model/terminal-3-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DeveloperPortal
  url: https://docs.terminal3.io
- type: Documentation
  url: https://docs.terminal3.io
- type: GettingStarted
  url: https://docs.terminal3.io/developers/adk/get-started/quickstart
- type: Support
  url: https://t.me/terminal3developer
- type: Blog
  url: https://blog.terminal3.io
- type: GitHubOrganization
  url: https://github.com/Terminal-3
- type: SignUp
  url: https://docs.terminal3.io/developers/adk/get-started/prerequisites/request-test-tokens
- type: TermsOfService
  url: https://terminal3.io/terms-of-service
- type: PrivacyPolicy
  url: https://terminal3.io/privacy-policy
- type: Website
  url: https://terminal3.io
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 23
  pass: local-v1

Terminal 3 API — frequently asked questions

Does Terminal 3 have an API?

Yes. APIs.io lists 7 APIs from Terminal 3, including Terminal 3 DID V1 API, Terminal 3 OpenID Connect V1 API and Terminal 3 OpenID Connect V2 API, and 4 more.

Is there an OpenAPI specification for the Terminal 3 API?

Yes. APIs.io indexes 7 OpenAPI specifications for Terminal 3, each linked for download from this page.

How do I authenticate with the Terminal 3 API?

Terminal 3 uses bearer-token authentication (http/apiKey · 2 schemes). The details are profiled on APIs.io as Terminal 3 Authentication.

Is the Terminal 3 API ready for AI agents?

Terminal 3 has a Kin Score of 44.2 out of 100 (developing) and an Agent Readiness score of 20.6 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/terminal-3"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/terminal-3/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/terminal-3/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.