The real-time data and action layer for AI agents.
One endpoint where agents search, verify, and act on real businesses — live availability, prices, and facts. Ranked, structured, and fresher every time an agent calls.
// agent → loop · one tool call search( "quiet outdoor table for 4, vegan options", "Kreuzberg, Berlin" ) // 2 results · ranked · machine-readable [ { "name": "Café Botanika", "availability": "likely_free_tonight", "confidence": 0.92, "vegan": true, "price_band": "€€", "observed": "2h ago" fresh }, { "name": "Hartmann's Garden", "availability": "call_to_confirm", "confidence": 0.74, "observed": "5h ago" } ]
Four tools. One endpoint.
Natural language in. Ranked, structured answers out. Built for tool calls, not human browsing.
Find, ranked
Natural-language query in — ranked, machine-readable results out, scored for fit.
Full record
The complete structured record for a chosen result — hours, menu, price, contact.
Freshness check
Confirm a single fact before acting — the latest observation and exactly when it was seen.
Close the loop
Tell Loop what happened. Agents that report outcomes earn fresher data and higher limits.
Every agent call makes the data better.
Demand, selection, and outcome signals flow back from normal usage. The data layer corrects itself — no scraping cron, no stale cache.
An agent asks in natural language — find, check, decide.
search() · verify()Ranked, structured results — each stamped with when it was seen.
confidence · observedThe agent books, reserves, or buys in the real world.
get_details()Outcome flows back. The data underneath corrects itself.
report()Built for agents, not maps.
Map APIs confirm a place exists. Agents need to know what’s true right now — in a shape they can act on.
Works where your agent lives.
Add Loop as an MCP server in one config line, or call the REST endpoint directly. Same data, same freshness, either way.
Loop speaks the protocols your stack already uses — drop it into any agent framework as a tool.
Named as contexts, not partnerships.
// remote MCP server — paste the URL into Claude (Settings → Connectors) // or add it to any MCP client: { "mcpServers": { "loop": { "url": "https://stayinloop.dev/mcp" } } } // then try: // "vegan dinner with outdoor seating in Kreuzberg tonight"
curl https://api.stayinloop.dev/v1/search \ -H "Authorization: Bearer $LOOP_API_KEY" \ -G \ --data-urlencode 'q=quiet vegan table for 4 tonight' \ --data-urlencode 'location=Kreuzberg, Berlin' # → 200 OK · ranked results, each with observed_at
Start free. Scale when your agents do.
Usage-based, no seats. Reporting outcomes earns fresher data and higher limits on every tier.
- All four tools
- MCP server + REST
- Community support
- Higher rate limits
- Priority freshness windows
- Report → reward limits
- Email support
- Custom limits & SLA
- Private endpoints
- Vertical onboarding