Offer to payout, in six steps.
Teleport owns the task, the requester and the proof. You own your performers. Requesters see Teleport, not your brand; the receipt records which lane did the work, so it's still auditable.
- 01
Offer
The router picks your lane and sends a signed offer: what, roughly where, by when, and the most it pays. Never who asked.
- 02
Quote
Optional. Price and ETA, at or under the ceiling. Answer a quote call within 5 seconds and you're scored on real numbers.
- 03
Accept
First accept wins. You get the exact place, access notes and, when the task needs it, a Teleport capture link for your performer.
- 04
Evidence
Your performer captures through the link, or you send your own proof. Teleport hashes what it stores.
- 05
Decision
Teleport verifies. Accepted work earns a Teleport PoPW receipt that names your lane; rejected work can come with a redo.
- 06
Paid
As soon as the requester's payment succeeds, Teleport pays you automatically, by Stripe transfer to your bank. A monthly statement shows every job.
Three ways in, one state machine.
Describe what you supply in one manifest: the kinds of performer, the work you take, where, how fast, and the evidence you can produce. Then start in the sandbox with a test key, run a dry run on real tasks, and go live once you pass the conformance kit.
| Push | Teleport POSTs signed events to your endpoint | Platforms with a backend |
| Pull | You poll /provider/events and /provider/offers | Behind a firewall, or a script |
| MCP | Your agent uses the provider MCP tools | Agent-native networks |
{
"schema": "teleport.provider.manifest/0.1",
"id": "acme-field",
"label": "Acme Field Services",
"url": "https://acme.example",
"kinds": ["HUMAN"],
"categories": ["INSPECT", "CAPTURE", "OBSERVE"],
"coverage": { "countries": ["US"], "regions": ["US-CA"], "areas": [], "remote": false },
"leadTimeMinutes": { "min": 60, "typical": 240 },
"evidence": { "origins": ["THIRD_PARTY_SUBMITTED"], "teleportCaptureLink": true },
"modes": ["push", "pull"],
"endpoints": { "events": "https://acme.example/teleport/events" },
"currency": "USD",
"support": { "email": "ops@acme.example" }
}Signed, private, and fair to your performers.
Signed both ways
Teleport signs every event with a key used for nothing else. Your calls carry your key and an Idempotency-Key, so a retry never does anything twice.
Least disclosure
Offers never name the requester, and the place stays within a kilometre or more until you accept. Exact addresses go only to the provider that took the job, only for that job.
Performers stay yours
Teleport never asks who your performer is. Receipts commit a salted hash of your own reference, nothing more.
Proof that names its source
Work captured through the Teleport capture link can reach the higher assurance tiers; your own proof of delivery is accepted and labelled as such on the receipt.
The spec, the schema, the vectors.
A public draft. Build against it, test with the vectors, and tell us what's missing: v0.1 is the time to change it.
| The spec | Markdown · the normative text |
| JSON Schema | 2020-12 · the manifest, every event and request |
| Test vectors | Signed events (valid and not) and example messages |
| Vectors script | Regenerates and checks the vectors |
Build it with teleport-tap-sdk/provider (a typed client and a ready events endpoint). Check it with npx -p teleport-tap-sdk teleport-provider-check. Or point an agent at https://mcp.teleport.eco/provider with your provider key.
How tasks are posted and verified: the protocol. Building on the requester side instead: Developers.
Providers
Bring your workforce.
We're onboarding provider platforms in small batches: human marketplaces, courier and field-service fleets, imagery networks and robot fleet operators. Tell us what you run and where. Approved providers get their sandbox and live keys by email.