06

The Developer Portal

The Trustline portal at portal.t54.ai is the operational home for onboarding, team governance, API keys, webhooks, transactions, challenges, and compliance.

The Trustline portal at portal.t54.ai is the operational home for the platform. You register, sign in with a verified email and password, and work inside an organization whose pages are gated by the role you hold. It serves two audiences from one place: institutions running agents complete KYB, govern their team, and reach compliance and audit evidence; agent developers issue and rotate API keys, configure webhooks, and inspect the transactions and challenges their integration produces.

This page is a high-level map, not the full reference. The complete, always-current developer documentation — the page-by-page guide, role permissions, transaction-detail views, and exact API contracts — is built into the portal itself: sign in and open the Docs page. The pages here cover public positioning and the contracts you need before you have an account.

What You Can Do in the Portal

AreaPagesWhat it covers
MonitorOverview, Transactions, Challenges, Request logs, SubjectsIntegration health at a glance, every underwriting decision, open Agentic Challenges, request debugging, and the entities observed in your traffic.
IntegrateAPI Keys, Configuration, WebhooksEnvironment-scoped credentials, per-environment settings, and signed event delivery.
GovernOrganization, Team, KYBYour tenant and its lifecycle, member invitations across five roles (owner, admin, developer, compliance, viewer), and business verification.
ProveCompliance, SettingsAudit-trace verification, evidence exports, organization settings, and the portal audit log.

Every action is role-checked server-side, so the navigation reflects what a member is allowed to do, and account access runs through standard sign-in, sign-up, email verification, password reset, and one-time invitation links.

Two Credentials, One Platform

Developers can integrate with Trustline entirely over the API — submitting transactions, answering challenges, and reading webhook deliveries never requires a browser. The portal is where the work that belongs to people happens. Two separate credentials keep these surfaces distinct, and they are not interchangeable:

  • Portal sessions authenticate people. A user signs in with a verified email and password; management requests under /api/v1/developer-portal/* carry the session token.
  • API keys authenticate workloads. The underwriting API accepts them; management endpoints never do. Keys are environment-scoped: tl_sandbox_ for sandbox and tl_production_ for production.

Sandbox is self-serve. Production access requires both approved KYB and Trustline-team enablement after a launch review; KYB approval alone does not unlock production. To start from a clean account, see Getting Started; for the public API contracts, see Async Underwriting API, Agentic Challenge, Webhooks and Monitoring, and Compliance and Audit.