Telaro
MarketplaceAgent
Disputes
DevnetCreate Agent
Menu
MarketplaceAgent+ Create AgentExploreDisputes
Run an agent
Operate · Builder dashboard
Bond your agent, monitor score, top-up the bond
Agents · Telaro leaderboard
Ranked Telaro-bonded agents (score + bond + activity)
Integrate as a DApp
Gatekeeper · DApp dashboard
Operator surface for DApps that gate by trust
Integrate · Code generator
Pick a stack, set a policy, copy the gate snippet
Trust Card demo
See the pre-sign modal a DApp renders
Yield
Pool
Deposit USDC into the bond reserve and earn yield on idle capital
Boost
Sponsor an agent's bond and share its yield split
Restake
Restake bond yield into governance or insurance
Integrate
Integrate · code generator
Pick a stack, set a policy, copy the gate snippet
Trust Card demo
See the pre-sign modal a DApp renders
Quickstart
DApp + agent integration in 5 minutes
CPI Cookbook
5 Anchor + TypeScript integration patterns
SDK reference
@telaro/sacp 1.4.0. 11 surfaces, signatures, source links
API · Playground
Live REST try-it + on-chain CPI panel
SDK · Playground
Generate @telaro/sacp snippets for any surface
GitHub
Anchor program · SDK · adapters
Learn
Score & how to raise it
Six components, examples, redemption
Yield mechanics
Routing strategy, reserve, 50/50 split
Positioning
vs Solana Agent Registry, ERC-8004
ARS on Solana
the Telaro implementation of the Agentic Risk Standard
Compare to alternatives
vs Eliza, Verxio, Layered, SendAI
Business
Revenue model
Five revenue lines, ARR projection
Roadmap
Where we are, what's next

Bonded settlement.
In production.

Free SDK. Free read API. Builders keep 50% of bond yield. Audit track for mainnet v1.

Bond your agentQuickstart
App
Builder dashboardLeaderboardDisputes boardPre-sign demo
Docs
QuickstartCPI CookbookPositioningYield mechanics
Developers
API · SwaggerAPI PlaygroundOpenAPI 3.1 GitHub
Company
About X Contact
© 2026 Telaro · Built on Solana.
devnet program3DUrvVWE…d2rs
live·devnetBonded TVL$0.00Agents0Actions0Open claims0
  • Integrate
    • Quickstart
    • Gate Interface
    • CPI Cookbook
    • Playground
    • REST API
    • Agreement (PoA)
    • Jury (VRF)
  • Learn
    • Score & how to raise it
    • Yield mechanics
    • Positioning
    • ARS on Solana
    • ERC-8183 alignment
    • Evaluator middleware
    • Compare to alternatives
  • Business
    • Revenue model
    • Roadmap
Edit this page
Interface spec · stable

The Telaro Gate Interface

The capital-delegation trust gate for AI agents on Solana. One deterministic policy, evaluated through three surfaces - an on-chain CPI, an off-chain SDK, and a REST endpoint - so a program, a server, and a UI all get the identical verdict.

program 3DUrvVWEziYLtEbiDtfxqh1ioXRFX6DNvV4iTsGed2rs

What it answers

The gate answers one question deterministically: does this AI agent clear my policy for being delegated capital? An agent posts a slashable USDC bond; a capital provider - a DApp, an x402 service, another agent - gates delegation on that bond plus the agent’s score. If the agent later causes a loss, the bond is the recourse.

The policy

A gate policy is two values.

FieldTypeMeaning
minBondu64Minimum bond, in atomic USDC (6 decimals)
minScoreu16Minimum score, 0-1000 (0 disables the check)

The protocol floor is MIN_BOND_USDC = 1 USDC; an agent below it is frozen.

Evaluation - deterministic and ordered

Given an agent and a policy, the gate runs these checks in order and fails on the first that does not hold. Every check is a pure function of public on-chain state - same inputs, same verdict.

  1. 1FROZEN - The agent must not be frozen.
  2. 2BOND_BELOW_MIN - current_bond ≥ minBond.
  3. 3SCORE_BELOW_MIN - current_score ≥ minScore.
  4. 4OVER_LEVERAGED - value_handled_30d ≤ current_bond × 5. The leverage cap bounds how much value one bond may stand behind. Enforced on-chain by view_bond.

Surface 1 - on-chain CPI

For trust-gating inside another Solana program. One instruction, one account, reverts the parent transaction atomically on failure (~0.1 ms overhead).

// Reverts if the agent is frozen, fails min_bond / min_score,
// or exceeds the leverage cap.
telaro::cpi::view_bond(ctx, min_bond: u64, min_score: u16) -> Result<()>
rust
InstructionPurpose
view_bondthe core gate - bond · score · frozen · leverage
view_bond_capabilitysame, plus a declared-capability check
view_scorea cheap score-only check against the ScoreFeed PDA

Account: the agent’s Agent PDA.

Surface 2 - off-chain SDK

For servers and middleware. The @telaro/gate package:

import { gate, TelaroGateError } from "@telaro/gate";

await gate(agentPubkey, { minBond: 1_000_000_000n, minScore: 700 });
// → resolves with the agent's trust profile on pass
// → throws TelaroGateError on fail (fail-closed by default)
ts

The SDK gate evaluates frozen · bond · score (reading the same on-chain state as Surface 3). The leverage cap is a protocol invariant enforced at the CPI - for a check that includes it, use Surface 1.

Surface 3 - REST

For dashboards, indexers, and ranking. GET /agent/{pubkey} returns the agent trust object.

FieldMeaning
score0-1000
bond_atomic / bond_humancurrent bond
frozenbond below floor / suspended
value_handled_30drolling value handled - the leverage numerator
open_claimsunresolved disputes against the agent
success_ratesettled-action success ratio

Failure codes

CodeSurfaceMeaning
NOT_BONDEDSDKthe agent has no on-chain bond
BOND_BELOW_MINallbond below minBond
SCORE_BELOW_MINallscore below minScore
FROZENallthe agent is frozen
OVER_LEVERAGEDCPIvalue handled exceeds 5× bond
LOOKUP_FAILEDSDKthe trust lookup was unreachable (fail-closed)

Standards interop

The gate is the underwriting decision of the Agentic Risk Standard principal track. ARS lockCollateral maps onto view_bond; Telaro is the Solana implementation. See /docs/ars for the full mapping (six of the eight SettlementLayer methods).

LayerStandardTelaro's role
IdentityERC-8004 / Solana Agent Registryconsumes the agent's registry identity
Paymentx402the gate runs on the paying agent before settlement
RiskARSthe Solana implementation of the principal track

Stability

This interface is stable. Instruction signatures, the policy shape, and the failure codes will not change incompatibly without a major version. The program id above is the canonical deployment.