TAP Provider Protocol · public draft v0.1

Plug your workforce into Teleport.

Run people, couriers, drones, dashcams or robots? Take physical work from the Teleport TAP Router through one signed protocol. You do the work and pay your people; Teleport verifies it and issues a Teleport PoPW receipt for every job.

The provider flow, as a sequence diagramTeleport sends a provider a signed offer with a $25 ceiling. The provider quotes $22 and 90 minutes, then accepts. Teleport sends the assignment with the place and a capture link, which the provider passes to its performer. The performer's evidence goes straight to Teleport through the link. Teleport sends the decision and the receipt, and later tells the provider the payment has cleared.TELEPORTPROVIDERPERFORMEROFFER · CEILING $25QUOTE $22 · ETA 90 MINACCEPTASSIGNMENT · PLACECAPTURE LINKEVIDENCE · TELEPORT_CAPTUREDECISION · RECEIPTPAYMENT CLEARED
Public draft · v0.1
§ 01

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.

  1. 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.

  2. 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.

  3. 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.

  4. 04

    Evidence

    Your performer captures through the link, or you send your own proof. Teleport hashes what it stores.

  5. 05

    Decision

    Teleport verifies. Accepted work earns a Teleport PoPW receipt that names your lane; rejected work can come with a redo.

  6. 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.

§ 02

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.

Modes
PushTeleport POSTs signed events to your endpointPlatforms with a backend
PullYou poll /provider/events and /provider/offersBehind a firewall, or a script
MCPYour agent uses the provider MCP toolsAgent-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" }
}
A manifest (teleport.provider.manifest/0.1) and a push endpoint that checks Teleport's signature
§ 03

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.

§ 04

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.

TAP Provider Protocol v0.1
The specMarkdown · the normative text
JSON Schema2020-12 · the manifest, every event and request
Test vectorsSigned events (valid and not) and example messages
Vectors scriptRegenerates 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.

Who does the work
Kinds of work