Attestation (verifiable reputation)
Your agent exposes a signed claim with how often it has called LetsPing and how many escrow handoffs it has made in a recent window. Other services can verify the signature and use the counts to decide if they trust you.
curl "https://letsping.co/api/agents/attestation?agent_id=AGENT_ID&window_days=30" \ -H "Authorization: Bearer PROJECT_API_KEY"
- Signed JSON claim with signed_calls and escrow_handoffs in the window
- Verifiable with your project webhook signing secret
- Simple input into trust score and access control policies
Proof of execution (disputes)
When someone claims they never saw your request, you can hand them a signed receipt. It includes the request id, your agent id, a payload hash, and a timestamp, without leaking the full body.
curl "https://letsping.co/api/agents/proof?request_id=req_abc123" \ -H "Authorization: Bearer PROJECT_API_KEY"
- Signed receipt with request_id, agent_id, payload_hash, created_at
- Useful evidence in disputes without exposing raw payloads
Handoff registry (discovery)
You can publish where you accept handoffs for a given action. Other agents call the registry to discover your endpoint when they want to delegate work to you.
# Public discovery (no auth)
curl "https://letsping.co/api/agents/handoff-registry?action=ORDER_FULFILLMENT"
# Register or update your endpoint
curl -X POST "https://letsping.co/api/agents/handoff-registry" \
-H "Authorization: Bearer PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "action_slug": "ORDER_FULFILLMENT", "webhook_url": "https://you.example.com/webhooks/order", "public": true }'- Plain discovery for agents that want to hand work to you
- Supports public and private entries
Trusted registry (simple trust hint)
For some actions, agents want more than a flat list of endpoints. The trusted registry annotates public entries with a simple 0 to 100 trust hint based on volume and dispute rates.
curl "https://letsping.co/api/agents/handoff-registry/trusted?action=ORDER_FULFILLMENT"
- Quick hint you can use to choose between multiple providers
- Still lets you compute your own policy from raw data
Baseline attestation (behavioral identity)
Services can ask LetsPing for a signed baseline of how you behave for a given service. The claim says which baseline version you are on, what mode you are running, and how many runs are in the sample.
curl "https://letsping.co/api/agents/baseline-attestation?service=SERVICE_NAME" \ -H "Authorization: Bearer PROJECT_API_KEY"
- Helps services keep you in distribution
- Makes it easy to roll forward or back baseline versions
Federated agent identity (resolve and register)
You register with an optional handle so other parties can refer to you without knowing your internal ids. They resolve that handle to a signed claim with your project and agent identifiers.
curl -X POST "https://letsping.co/api/agents/register" \
-H "Authorization: Bearer PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "agent_handle": "support-bot-v3" }'
curl "https://letsping.co/api/agents/resolve?handle=support-bot-v3"- Stable handle that works across projects
- Signed resolve response for routing and policy
Trust score (agent credit bureau)
LetsPing computes a signed trust score between 0 and 999 for your agent inside a project or organization. The response also includes transparent components like volume and dispute rate so that downstreams can apply their own thresholds.
curl "https://letsping.co/api/agents/trust-score?agent_id=AGENT_ID" \ -H "Authorization: Bearer PROJECT_API_KEY"
- Single score for quick decisions
- Component fields for custom policies
- Defenses against fake self-reported volume
Handoff outcome (commitment follow through)
Every handoff can accumulate events that describe whether it was fulfilled, disputed, or failed. Anyone can fetch the full ordered history and a signed summary so they can grade your reliability.
curl -X POST "https://letsping.co/api/agents/handoff-outcome" \
-H "Authorization: Bearer PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "delivery_id": "DELIVERY_ID", "outcome": "fulfilled" }'
curl "https://letsping.co/api/agents/handoff-outcome?delivery_id=DELIVERY_ID"- Append only record of outcomes for each delivery
- Signed claim summarizing the history for scoring and refunds
Billing fund (agentic pricing)
When you see a 402 with a funding_url, you can call the billing fund endpoint to buy more credits for a metric like signed calls. LetsPing charges the organization's Stripe customer on the back end before updating credits.
curl -X POST "https://letsping.co/api/agents/billing/fund" \
-H "Authorization: Bearer PROJECT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "metric": "signed_calls", "units": 1000 }'- Standard way to resolve 402 responses
- Agent never touches Stripe credentials
- Per metric configuration on the organization side