The real world doesn’t have an API. We built one.
Phone calls, payments, errands, and services. Your agent sends one request. The task gets done, and the outcome comes back as data.
30M+ real-world actions completed. REST API and MCP. Bring your own agent, or use ours.
My flight was delayed 4 hours. Get me a refund.
United approved a $847 refund. It’s back on your card in 5 to 7 days.
Agents can do a lot. They can’t do everything.
Your agent isn’t unreliable. The real world is.
- The office doesn’t pick up before 10am. Or after 3.
- The vendor takes checks. Only checks.
- One item isn’t available. Substitute or wait?
- The hours changed. Nobody updated the listing.
- The counter agent is new and can’t find the reservation.
- Three departments. Three hold queues. One resolution.
AI alone fails 63% of complex real-world tasks.
With Duckbill, the same task types resolve 93% of the time.
Your users don’t care who did it. They care that it’s done.
Four capabilities. One API.
Start with phone calls. Your users will ask for the rest.
Phone calls
AI can make phone calls now. People still hang up.
- Get the refund United owes for the 4-hour delay.
- Book a dermatologist who takes Aetna, weekday afternoons.
- Find out why the claim was denied. Then appeal it.
Payments
Your agent got blocked at checkout. Hand us the payment.
- Pay the caterer’s $1,200 deposit by phone.
- Mail the check the contractor insists on.
- Finish the order that blocked your agent at checkout.
Errands & services
Your agent can’t show up. Someone has to.
- Pick up the dry cleaning before they close at 6.
- Return the couch. Yes, the whole couch.
- Be there when the plumber shows up between 2 and 6.
Concierge
Haven’t built an agent yet? Use ours.
- We’re moving to Austin in six weeks. Handle all of it.
- Plan the birthday: 15 kids, nut allergy, under $400.
- Get me a plumber this century.
You ping the API. The task gets done.
One request in. Status while it runs. A verified outcome back. Everything in between is our problem, not yours.
- 1Send the goalPlain language. Who it’s for, what done looks like, a ceiling if money moves.
- 2Watch it runAttempted, connected, resolved. Your agent can add context mid-task.
- 3Get the outcomeStructured, not a vibe. What happened, who handled it, confirmations, amounts.
REST API with webhooks, or the Duckbill MCP server for Claude, ChatGPT, and agent frameworks. MCP docs
Three layers. AI owns one.
Every real-world task has three layers. Models have mastered the first. Duckbill runs the other two.
- Layer 3DuckbillMaking it happenCalls, payments, pickups, negotiations, follow-ups. 33M US businesses have no API. This is where AI products break, and where Duckbill operates.
- Layer 2DuckbillReal-world intelligenceWho picks up at 9am. Which line gets you a person. What triggers a callback. None of it can be scraped. We learned it from 30M+ real interactions.
- Layer 1AIThe planUnderstanding the goal, breaking it into steps, putting them in order. Your model already does this well.
Human where it matters. AI where it finishes.
Most products bolt on a human for when the agent fails. Here it’s the architecture. Every step goes to whatever finishes it reliably, a model or a person, and 30M+ real-world actions taught us which is which.
calls AI finishes working alone.
calls a person finishes, or redoes after the business hung up on AI.
We’re building the ground truth of the real world.
Every task we finish produces data no one else has. Each decision point teaches the system how the physical world actually works. Pick a task and watch.
Different tasks. Same building blocks.
Every step is a place the real world can say no.
- 01researchFind hours and policies
- 02digitalCall to confirm order ready
- 03fixNegotiate missing item
- 04transactionPay over the phone
- 05fixItem wasn’t ready. Call back
- 06in personPick up
6 tasks. 5 kinds of step. 36 steps. Select a task to see them in order.
Questions
What is Duckbill?
Duckbill is an execution API for AI agents. It gets real-world tasks done: phone calls, payments, errands, and services. Your agent sends the goal, Duckbill completes it and returns the outcome. The infrastructure behind it has handled 30M+ real-world actions.
Who is Duckbill for?
Two kinds of customers. AI agents and assistants that need reliable execution for their end users, and companies that want real-world tasks handled end to end without building an agent of their own. The first group integrates the capability APIs. The second uses Concierge.
How do I integrate Duckbill?
Through a REST API with webhooks, or through the Duckbill MCP server for Claude, ChatGPT, and agent frameworks. Most teams start with phone calls and add payments and errands as their users ask for them.
Does Duckbill use humans?
Yes, where it matters. Every step goes to the cheapest model or person that can finish it reliably, and a person stands behind the automation wherever it runs out. The routing is our problem, not yours. You ping the API. The task gets done.
How much does Duckbill cost?
A simple per-task fee. No specialists to hire, no BPO to manage, no ops team on your balance sheet. Tell us your volume and we will send pricing.
Don’t become a services company.
Stripe meant you didn’t have to become a payments company to take payments. Duckbill means you don’t have to become a services company to get things done in the real world. No specialists to hire. No BPO to manage. Ping the API, pay per task.
REST API and MCP. Bring your own agent, or use ours.
