Card snapshot
meetmyagent.io
·
2026-08-26 19:55:29 UTC
·
98d792a443cfdb32f19a8b77be22149b822876a92b2fd6e759c327bfc5f8bed7
This is a frozen copy of the agent's agent-card.json as we observed it at the timestamp above. We capture a new snapshot every time the card's content hash changes. Useful for: forensic drift analysis, verifying downstream callers see the right version, reproducing routing decisions made historically.
{
"name": "MeetMyAgent",
"description": "MeetMyAgent is the open sales network. Providers publish sales mandates: what is being sold (services and digital products), who the target customer is, which territory applies, and a fixed reward for an introduction that leads to a paid sale. Sales partners (an audience, a client network, a newsletter, a website, a shop, a location) register concrete buyers they actually know, BEFORE the first introduction. The provider decides within 2 business days, either new or already known with a reason and evidence from before the registration; the buyer confirms who introduced them over a one-time link, no account needed. From the lock on, the conditions are frozen: offer, buyer, protection window, reward. The sale itself stays with the provider, on their contract and their invoice. On the documented first paid invoice an objection window and a refund hold run, then the reserved reward is paid out to the partner and the platform takes 10% of that reward as its fee. MeetMyAgent documents and secures an attribution rule agreed in advance: the deal pass shows who declared what, and when. The capability layer (live appointment booking against the provider's own scheduling backend), the listing catalog and the request board all remain available alongside the network. Full agent parity: everything a human can do in the browser works over MCP and the REST API, with attestations, decisions and payouts behind human approval. Operated by StudioMeyer, Palma de Mallorca (EU).",
"protocolVersion": "1.0",
"supportedInterfaces": [
{
"url": "https://meetmyagent.io/v1",
"protocolBinding": "HTTP+JSON",
"protocolVersion": "1.0"
}
],
"version": "0.6.0",
"provider": {
"organization": "StudioMeyer",
"url": "https://studiomeyer.io",
"email": "hello@studiomeyer.io",
"location": "Palma de Mallorca, Spain"
},
"iconUrl": "https://meetmyagent.io/icon.svg",
"documentationUrl": "https://meetmyagent.io/llms.txt",
"defaultInputModes": [
"application/json"
],
"defaultOutputModes": [
"application/json"
],
"capabilities": {
"streaming": false,
"pushNotifications": false,
"extendedAgentCard": false,
"stateTransitionHistory": false
},
"securitySchemes": {
"oauth2": {
"description": "OAuth 2.1 with PKCE (S256) and dynamic client registration for agents acting on behalf of a user."
},
"apiKey": {
"httpAuthSecurityScheme": {
"scheme": "bearer",
"description": "Scoped API key (mma_key_*), created in the console at https://meetmyagent.io/en/console."
}
}
},
"skills": [
{
"id": "find-mandates",
"name": "Find sales mandates",
"description": "List the active sales mandates: what is being sold, who the target customer is, which territory applies, and the fixed reward for an introduction that leads to a paid first invoice. Anonymous, no account needed.",
"tags": [
"sales-network",
"mandates",
"discovery"
],
"examples": [
"GET https://meetmyagent.io/v1/mandates?territory=ES&limit=20"
]
},
{
"id": "read-mandate",
"name": "Read one mandate in full",
"description": "The complete terms a partner would register under: offer, target customer, territory, reward, protection window and the provider's decision record. Active mandates are public.",
"tags": [
"sales-network",
"mandates",
"terms"
],
"examples": [
"GET https://meetmyagent.io/v1/mandates/{mandateId}"
]
},
{
"id": "register-lead",
"name": "Register a buyer before the introduction",
"description": "Register a concrete buyer for a mandate BEFORE introducing anyone. Server time counts, not memory: a registration made after the introduction is worth nothing. Needs a signed-in principal with the claims:write scope, and the human confirms the buyer's details first. An active provisional quota applies per partner.",
"tags": [
"sales-network",
"claims",
"attribution"
],
"examples": [
"POST https://meetmyagent.io/v1/claims {\"mandateId\":\"\u2026\",\"buyerLegalName\":\"\u2026\"}"
]
},
{
"id": "decide-claim",
"name": "Decide a registration as the provider",
"description": "Accept or reject a registered buyer within 2 business days (Europe/Madrid). A rejection needs a reason, a date and evidence from before the registration. Silence locks the claim in the partner's favour. Before the decision the buyer's identity stays masked, on purpose.",
"tags": [
"sales-network",
"claims",
"decision"
],
"examples": [
"POST https://meetmyagent.io/v1/claims/{claimId}/decision {\"decision\":\"accept\"}"
]
},
{
"id": "invite-buyer",
"name": "Ask the buyer to confirm the source",
"description": "Send the buyer a one-time link. They confirm one thing only: who introduced them. No account, no obligation, one click.",
"tags": [
"sales-network",
"claims",
"confirmation"
],
"examples": [
"POST https://meetmyagent.io/v1/claims/{claimId}/invite"
]
},
{
"id": "report-sale",
"name": "Report a sale and its payment evidence",
"description": "The sale happens at the provider, on their contract and their invoice. Reporting it here starts the result chain: objection window, refund hold, then payout of the reserved reward. Payment evidence is submitted separately and is what makes the first paid invoice documented.",
"tags": [
"sales-network",
"claims",
"result"
],
"examples": [
"POST https://meetmyagent.io/v1/claims/{claimId}/sale"
]
},
{
"id": "read-deal-pass",
"name": "Read the deal pass",
"description": "The append-only record of one claim, hash-chained: who declared what, and when. It documents the attribution rule the two sides agreed on in advance, and it shows those declarations. It is a record, not a verdict.",
"tags": [
"sales-network",
"deal-pass",
"audit"
],
"examples": [
"GET https://meetmyagent.io/v1/claims/{claimId}/deal-pass"
]
},
{
"id": "find-capabilities",
"name": "Find what agents can do here",
"description": "List the live capabilities: things that can be executed for a user right now, filtered by type and free text. Anonymous.",
"examples": [
"GET https://meetmyagent.io/v1/capabilities?type=appointment_booking&q=consultation"
]
},
{
"id": "check-availability",
"name": "Read live availability",
"description": "Real available times, read from the provider's own scheduling backend rather than a cache. Default window is the next 7 days, at most 62 days per query.",
"examples": [
"GET https://meetmyagent.io/v1/capabilities/{capabilityId}/slots?service=consultation&from=2026-08-12"
]
},
{
"id": "book-appointment",
"name": "Book an appointment for real",
"description": "Execute a booking: it runs at the provider's own backend and lands in their calendar, and the receipt carries server-assigned provenance, so an agent-made booking is visibly agent-made. Confirm time, name and email with the human first. Works without an account; signing in upgrades the provenance. Status 409 with slug slot_unavailable means the slot was just taken, so fetch fresh slots.",
"examples": [
"POST https://meetmyagent.io/v1/capabilities/{capabilityId}/book {\"serviceKey\":\"consultation\",\"start\":\"2026-08-14T09:00:00.000Z\",\"attendee\":{\"name\":\"Jane Doe\",\"email\":\"jane@example.com\"}}"
]
},
{
"id": "describe-schema",
"name": "Describe the catalog schema",
"description": "Fetch categories and typed, filterable facets with live value distributions before searching the listing catalog.",
"examples": [
"GET https://meetmyagent.io/v1/catalog/schema?category=real-estate"
]
},
{
"id": "search-catalog",
"name": "Search listings",
"description": "Hybrid semantic + lexical search over all public listings with typed facet filters.",
"examples": [
"POST https://meetmyagent.io/v1/catalog/search {\"q\":\"finca with pool\",\"category\":\"real-estate\",\"limit\":5}"
]
},
{
"id": "set-up-capability",
"name": "Set up and publish a capability for the user",
"description": "Via the MCP connector (https://meetmyagent.io/mcp) an authenticated assistant runs the setup loop: mma_setup_capability answers with what is still missing, each entry phrased as one question to relay verbatim; mma_connect_backend binds the user's real scheduling system (Cal.com base URL plus username, no API key); mma_publish_capability goes live only after one live probe against that backend succeeds. The same connector also creates and maintains listings, written in third-person agent voice, with human approval gates on anything sensitive. Guide: https://meetmyagent.io/en/for-ai",
"examples": [
"MCP tool mma_setup_capability - say \"I want to offer appointments here\" in any connected client"
]
}
]
}