Send a video to a real person and get back their recorded reaction — verifiable proof a human actually watched, on demand. Reapption is the human-attention layer for your agent.
Self-serve. Your agent registers itself and starts in seconds — POST /api/agent/register
Machine-readable: /openapi.json · /llms.txt · /docs/agent-api
One task, start to finish: the agent creates it, a person reacts, the signed result comes back.
Hand off any video with one API call and get a single-use link back.
Get a timestamped, on-camera reaction — proof, not a click.
Fully machine-to-machine until one person is asked to react.
Four steps, start to finished reaction. Your agent drives the whole thing over HTTP.
Your agent answers a quick reasoning challenge and gets an API key. No signup form, no human.
POST a payload video. You get a one-time, expiring link to hand to a person you already reach.
The human opens the link, watches, and records — on a login-free page in any mobile browser.
Retrieve the reaction video plus metadata, or receive a signed webhook the moment it's ready.
Create a task, hand off the link, poll or wait for the webhook, retrieve the video.
# register once: answer a challenge, get an API key curl -X POST https://reapption.net/api/agent/challenge curl -X POST https://reapption.net/api/agent/register \ -H "Content-Type: application/json" \ -d '{"name":"my-agent", ...challenge answers}' # dry run in CI — no human, never billed curl -X POST https://reapption.net/api/agent/tasks \ -H "X-Agent-Key: agt_…" -H "Content-Type: application/json" \ -d '{"sandbox":true}' # create a real task with a payload video curl -X POST https://reapption.net/api/agent/tasks \ -H "X-Agent-Key: agt_…" \ -F payload=@clip.mp4 \ -F webhook_url=https://my-agent/hook # → { task_id, react_url } — send react_url to a human # retrieve when ready curl https://reapption.net/api/agent/tasks/$ID \ -H "X-Agent-Key: agt_…" # → reaction_url, duration, timestamp…
Every react link is an unguessable, expiring, one-time token. It can't be replayed or shared onward.
Completion callbacks are HMAC-signed with your secret, so you can safely act on them — including releasing payment.
ready, expired, or failed — you always know whether to wait, retrieve, or move on.
Every reaction comes with its sha256 and exact file_size, served from reapption.net — hash what you downloaded before you pay out.
GET /tasks/:id/receipt returns an Ed25519-signed receipt — task, time, duration, video hash, the human's answer — verifiable offline against /.well-known/jwks.json.
Add a question (with optional choices) and the human must answer it after watching — proof of understanding, not just attention.
A react link is for one person. A campaign is one public URL for a post, a group chat or a contest: every reaction becomes its own single-use task.
# one public URL, up to 50 reactions curl -X POST https://reapption.net/api/agent/campaigns \ -H "X-Agent-Key: agt_…" -H "Content-Type: application/json" \ -d '{"payload_url":"https://…/clip.mp4", "max_reactions":50, "question":"Where did the ball go?", "webhook_url":"https://my-agent/hook"}' # → { campaign_id, url: "https://reapption.net/c/…" } # reconcile: counts and every reaction curl https://reapption.net/api/agent/campaigns/$ID \ -H "X-Agent-Key: agt_…" # signed settlement receipt over every ready reaction curl https://reapption.net/api/agent/campaigns/$ID/receipt \ -H "X-Agent-Key: agt_…"
Nothing is created until a reaction comes in, so an unused campaign or a visitor who leaves costs nothing.
Dedupe is on by default: one reaction per payout_address. Cap it with max_reactions and a TTL of up to 7 days.
Every reaction is a normal task with its own webhook and receipt; the campaign receipt signs the whole set. Reapption never sends funds: paying is yours.
Test it, monitor it and operate it from code. No dashboard, no human.
"sandbox": true tasks complete themselves (as ready, failed or expired), fire the real signed webhook, and are never billed. Test the whole flow in CI.
GET /api/agent/me confirms your key and shows your remaining quota and task counts. Every 429 carries Retry-After.
GET /api/agent/tasks?status=pending,ready lists your tasks with their links, so a lost task_id or react_url is one call away.
POST /api/agent/rotate-key swaps your key with a short overlap; POST /api/agent/revoke shuts a leaked agent down and kills its pending links.
Every delivery attempt is logged for 30 days. POST /tasks/:id/webhook/replay sends one again with a fresh signed link.
POST /api/agent/webhooks/test sends a signed test to your receiver before any human reacts. A 403 means a wrong secret.
Pure infrastructure. You keep the relationship, the judgment, and the payment.
An on-camera video reaction is a far harder receipt to fake than a "watched: true" flag. You get the actual footage.
Reapption proves a fresh human reaction was captured. Whether it's sincere, on-topic, or worth paying for is your call — run your own model on the video.
You deliver the link in your own channel. Reapption never learns who your human is or how you reach them.
Register programmatically and start immediately. A free tier to prototype; scale when you're ready.
Anywhere a click isn't enough and you need a person to genuinely watch.
Read the docs and make your first call in minutes.