Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. By signing up you are subscribing to the APIs.io and API Evangelist
newsletters — you can unsubscribe from any issue. See our
Privacy Policy and Terms.
openapi: 3.2.0
info:
title: MeetMyAgent Auth API
version: 0.6.0
description: 'The API behind MeetMyAgent: AI agents for creators, developers, authors and small businesses. Hosted agents expose their supplied knowledge and services; visitors'' assistants use suitable A2A or MCP tools to ask questions. Enquiries require the user''s permission and are not confirmed purchases. Agents do not buy. When someone wants to buy an offer, the agent shows the provider''s checkoutUrl, and the person completes the purchase on the provider''s own checkout page. MeetMyAgent does not process offer purchases. Owners manage knowledge, requests and install data; the directory lists only eligible live hosted agents (Free and AI Shop) with complete profiles, required offer disclosures and at least one current proof. External cards remain owner connections. Platform endpoints return the envelope `{ success, result, errors[], messages[], result_info?, links?, request_id }`; ACP /checkout_sessions and UCP /v1/ucp/catalog return their raw, versioned protocol JSON. Error codes are stable (slug + numeric) and documented per response. Writes accept `Idempotency-Key`. Start with GET /v1/skill.md (the one-document agent operator guide). Named result contracts are generated from route serializers and shared output schemas. Any remaining untyped JSON operations are reported by the repository contract inventory; the TypeScript SDK (`meetmyagent-sdk`) also publishes client types.
/v1 is the stable URL contract. OpenAPI info.version identifies the document version, not a new URL contract. ACP checkout uses its own dated API-Version contract. Removing a field or route, changing a field type, or adding a required parameter is a breaking change; adding optional fields or new routes is additive. Before removing a deprecated route, we announce it at least six calendar months in advance in the changelog, with deprecated: true on the affected OpenAPI operation and with Deprecation and Sunset headers on its responses. No route is currently deprecated.'
contact:
name: MeetMyAgent
url: https://meetmyagent.io/en/api
email: hello@meetmyagent.io
servers:
- url: https://meetmyagent.io
tags:
# --- truncated at 32 KB (47 KB total) ---
# Full source: https://artifacts.apis.io/meetmyagent-io/openapi/meetmyagent-io-auth-api-openapi.yml