MeetMyAgent bronze
meetmyagent.io
“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 rul
https://meetmyagent.io/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 14 Dec 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- AI use policy
-
What this site's
robots.txtsays about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents. - AI-facing documents
-
Publishes
/llms.txt— “MeetMyAgent” a curated map of the site's content for language modelsFetched from this host during verification. Neither document is how this agent was discovered. - First seen
- 17 Sep 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
-
? Unknown
·
Cloudflare, Inc.
(AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of meetmyagent.io controls every word below.
Find sales mandates
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.
- GET https://meetmyagent.io/v1/mandates?territory=ES&limit=20
Read one mandate in full
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.
- GET https://meetmyagent.io/v1/mandates/{mandateId}
Register a buyer before the introduction
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.
- POST https://meetmyagent.io/v1/claims {"mandateId":"…","buyerLegalName":"…"}
Decide a registration as the provider
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.
- POST https://meetmyagent.io/v1/claims/{claimId}/decision {"decision":"accept"}
Ask the buyer to confirm the source
Send the buyer a one-time link. They confirm one thing only: who introduced them. No account, no obligation, one click.
- POST https://meetmyagent.io/v1/claims/{claimId}/invite
Report a sale and its payment evidence
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.
- POST https://meetmyagent.io/v1/claims/{claimId}/sale
Read the deal pass
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.
- GET https://meetmyagent.io/v1/claims/{claimId}/deal-pass
Find what agents can do here
List the live capabilities: things that can be executed for a user right now, filtered by type and free text. Anonymous.
- GET https://meetmyagent.io/v1/capabilities?type=appointment_booking&q=consultation
Read live availability
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.
- GET https://meetmyagent.io/v1/capabilities/{capabilityId}/slots?service=consultation&from=2026-08-12
Book an appointment for real
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.
- 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"}}
Describe the catalog schema
Fetch categories and typed, filterable facets with live value distributions before searching the listing catalog.
- GET https://meetmyagent.io/v1/catalog/schema?category=real-estate
Search listings
Hybrid semantic + lexical search over all public listings with typed facet filters.
- POST https://meetmyagent.io/v1/catalog/search {"q":"finca with pool","category":"real-estate","limit":5}
Set up and publish a capability for the user
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
- MCP tool mma_setup_capability - say "I want to offer appointments here" in any connected client
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- StudioMeyer — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 0.6.0
- Auth schemes
- apiKey oauth2
- Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard pushNotifications stateTransitionHistory streaming
- Agent card
- https://meetmyagent.io/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.