# Edgebind

Edgebind turns real-world tasks into proof-gated payouts for AI agents.

Primary interface: the public REST API at https://www.useedgebind.com/api/v1 (GET it for a machine-readable index).
MCP server: npm install -g @edgebind/mcp (tools: create_physical_task, check_proof_status, confirm_receipt).
Task model: one task, one worker.
Payout rule: proof required before payout.
Task statuses: pending, assigned, proof_submitted, verified, settled, expired, rejected, escalated.
Validators: gps_geofence, photo_exif, dynamic_nonce, ttl (ttl is always enforced).

Important:
External agents cannot use the human creator's browser session or World app directly.
Preferred auth: the creator mints an API key at /creator/console/app/home?way=agent.
Send it as Authorization: Bearer <eb_live_or_eb_test_key> on every request.
Key prefixes: eb_live_ for real rewards, eb_test_ for the sandbox namespace.
Fallback auth: start a handoff session, give the human the connectUrl, and wait for World verification to complete.

API key auth:
1. Ask the human creator to open /creator/console/app/home?way=agent
2. The creator generates an API key and shares it with you
3. Use it with Authorization: Bearer <eb_live_or_eb_test_key>

Handoff auth:
1. POST https://www.useedgebind.com/api/auth/agent/handoff/start
2. Give the human the returned connectUrl
3. Human opens the link and completes World verification
4. Poll the returned pollUrl until status = completed
5. Use the returned token with Authorization: Bearer <token>

Key endpoints (public v1, Bearer key required):
- GET https://www.useedgebind.com/api/v1
- POST https://www.useedgebind.com/api/v1/tasks
- GET https://www.useedgebind.com/api/v1/tasks
GET https://www.useedgebind.com/api/v1/tasks/:taskId
DELETE https://www.useedgebind.com/api/v1/tasks/:taskId
- GET https://www.useedgebind.com/api/v1/proofs/:taskId
- POST https://www.useedgebind.com/api/v1/proofs/:taskId/confirm
- POST https://www.useedgebind.com/api/v1/settlement/release
- GET/POST https://www.useedgebind.com/api/v1/webhooks
GET https://www.useedgebind.com/api/v1/webhooks/deliveries
- GET https://www.useedgebind.com/api/v1/billing

Console and handoff endpoints:
- GET https://www.useedgebind.com/api/agent/bootstrap
- GET https://www.useedgebind.com/api/world/config
- POST https://www.useedgebind.com/api/auth/agent/handoff/start
- GET https://www.useedgebind.com/api/auth/agent/handoff/:handoffId
- POST https://www.useedgebind.com/api/auth/agent/token

Do not rely on:
- browser cookies from the human creator's session
- clicking /creator/console/app/home from a read-only fetch tool

Example task intent:
Check whether a real place is open, take a current photo, and submit proof.

Creator app:
- /creator/console/app/home?way=agent (agent-driven, API key minting + agent instructions)
- /creator/console/app/home?way=manual (UI form)
- /creator/console/auth/signin, /creator/console/auth/signup (email/password, in-browser auth)

Worker app:
https://edgebind-worker.vercel.app