APIs, tools and merchants AI agents can actually use. Every badge is probe-backed, never self-asserted.
Tool-calling runtime with per-user OAuth, so agents act as the signed-in user across third-party APIs
Issue tracking and project data over GraphQL and a remote MCP server agents can drive
Storefront, Customer Account, Checkout, and Dev MCP servers plus ACP and UCP support across millions of merchants
Connected Apps and M2M auth — treat each agent as its own OAuth client, and stand up OAuth-compliant MCP servers
AuthKit, Connect, and MCP auth — OAuth flows, scoped tokens, and bot detection for agent access
Work graph — tasks, projects, and portfolios — over REST and a remote MCP server
Jira issues and Confluence pages over REST and a remote MCP server
Token vault, async user approval, and Cross App Access for agents calling third-party APIs
CRM records, deals, and marketing data over API and a hosted MCP endpoint
Support inbox, tickets, and conversations over API and a remote MCP server
Code-first integration platform handling OAuth, syncs, webhooks, and tool definitions agents call
Read and write Notion pages and databases via API or the remote MCP server — durable agent knowledge base
Identity-layer protocol (XAA) giving enterprises visibility and policy control over which apps an agent may reach
Agent-ready checkout and payouts, an ACP payment provider, plus a remote MCP server over the PayPal APIs
Catalog, orders, and payments APIs for merchants, with a remote MCP server
Same query as JSON: /api/v1/services?has_llms_txt=true&auth_method=m2m-oauthAdd to Claude Code:claude mcp add botfriendly …