Proof flow
Callable API example flow
Haunt API is the flagship callable API example because its service card, Markdown summary, and category funnel are already public.
GET /agent-index.jsonFetch the agent route map.
SearchGET /api/search?q=web%20extraction%20apiFind services by problem and capability.
Open funnelGET /category-funnels.jsonSee web_extraction.primary_service_id=haunt-api.
Inspect JSONGET /services/haunt-api.jsonRead the callable API service card.
Inspect MarkdownGET /services/haunt-api.mdUse the concise Markdown rendering for page-level context.
Agent need: extract company website data to JSON
Search: GET /api/search?q=website%20to%20json
Inspect: GET /services/haunt-api.json
Boundary: only recommend when public webpage extraction is a fitHonest boundaries
- The catalog is curated and early, not a universal API marketplace.
- Callable status varies by listing. Some services are callable APIs, some are manual review only, concierge services, dashboards, local tools, or owner-reviewed listings.
- OpenInvoke does not replace API docs, auth docs, official SDKs, or the provider's own terms.
- Do not imply every submitted API will be approved, verified callable, or ranked highly.
Example service IDs
Measurement
Privacy-safe activation markers
These pages expose data attributes for activation reporting. They identify route, link target, query class, service ID, format, package, and category. They do not expose raw IPs, emails, raw user agents, raw lead IDs, or private review notes.
- organic_page_view: route=/agent-readable-api-directory, source_class, campaign_class, landing_route
- catalog_search_started: route=/agent-readable-api-directory, query, search_surface=api
- category_funnel_opened: route=/agent-readable-api-directory, category=web_extraction, primary_service_id=haunt-api
- service_card_inspected: route=/agent-readable-api-directory, service_id, format=json|markdown
- api_listing_submission_intent: route=/agent-readable-api-directory, package=Free listing|Verified callable|Not sure yet
