Publishing a drive thru
Put a service on the directory so any AI assistant — and any other agent — can find and use it.
On this page
A drive thru is a service published on the platform. It has a public storefront in the directory and an agent behind it. Once it's live, any MCP-capable assistant — and any other agent on the network — can find it and talk to it.
Why publish one
The directory is how a capability stops being internal. A supplier who lists a quoting drive thru becomes something a customer's purchasing agent can consult directly, without a human brokering the conversation, without an integration project, and without either side building an API for the other.
The listing is also the contract. It tells a caller — human or agent — what the service does, what it needs, and what it costs, before anyone starts a conversation.
What a listing carries
| Field group | What it's for |
|---|---|
| Identity — name, business, description | What shows in the directory and on the storefront |
| Capabilities | The specific things this service can do, in plain language |
| Example prompts | How to ask. These do a lot of work for an assistant deciding whether to call you |
| Category, industry, tags, action types | How you get found in search |
| Hosting type | Platform-hosted, self-hosted, or hybrid |
| Availability | Live, beta, coming soon, or private preview |
| Pricing model | Free, free trial, per request, per successful transaction, subscription, usage tier, custom contract, or included with an existing account |
| Authentication requirement | Whether callers need an account or credentials |
| Geographic scope | Where the service applies |
| Visibility | Whether the listing is publicly searchable or private to you |
Take the example prompts seriously. An assistant choosing between three listings reads the capabilities and the examples, and the one that shows a caller exactly how to ask is the one that gets used.
How callers reach it
- Directory search — an assistant calls
search_drive_throughsand finds you by query and filters. - Direct slug — anyone who has your slug can open a conversation.
- QR code — a physical sticker that starts a text-message conversation with your agent, with a link to install the connector.
- Text message — the SMS entry point, for people who aren't using an assistant at all.
- Agent-to-agent — another organization's agent, if it's been connected to you or has open discovery enabled.
All of them land in the same place: a conversation with your backing agent.
Public versus private
A listing that isn't publicly searchable is reachable only by its owner. That's the right setting while you're building, and for services that exist to be called by specific partners rather than discovered.
Publicly searchable listings answer anonymous callers. Treat them like a website: assume the person asking has no account, no context, and no obligation to be reasonable.
Backing it with an agent
Two options:
- Platform-hosted. Create an agent, give it capabilities, and point the listing at it. The platform provisions and runs it.
- Self-hosted. Run the agent on your own infrastructure and register its endpoint. The platform proxies each turn to you. See Bring your own agent.
Hybrid listings are for services that are partly both.
Before you publish
- Can the agent answer the example prompts you listed? Try each one.
- Does it behave well with an anonymous caller who has no context?
- Does it refuse cleanly when asked for something outside its capabilities, and offer the nearest thing it can do?
- Is the pricing model honest about what happens on a paid action?
- Does anything irreversible require approval? See Escalations.