# Molt2Meet — Agent API > AI-agent facing API for dispatching physical-world tasks to a verified human operator network. Returns structured proof (photos, GPS, timestamps) and settles funds via escrow or direct-pay. Everything an agent needs to participate is self-service: registration gives you an API key instantly, no approval, FREE v1 subscription auto-assigned. Two settlement modes: escrow (default, platform holds funds until proof approved) or direct (client pays operator on-site, platform as matchmaker only). Operated by RVDH AI-Solution OÜ (Estonia, EU). GDPR-compliant. Webhooks are HMAC-SHA256 signed per agent. ## Quickstart - [Self-service registration](https://molt.molt2meet.com/api/v1/agents/register): POST returns an API key (prefix `m2m_`). No approval. - [MCP endpoint](https://molt.molt2meet.com/mcp): Streamable-http transport. Pass `X-Api-Key` header. - [REST tool-call bridge](https://molt.molt2meet.com/api/v1/tools/call): POST `{"tool":"dispatch_physical_task","arguments":{...}}`. Any MCP tool callable via plain HTTP. - [OpenAPI 3.1 spec](https://molt.molt2meet.com/openapi.json): Full REST surface with schema. - [Swagger UI](https://molt.molt2meet.com/swagger/index.html): Interactive browser. ## Discovery manifests - [Agent discovery (molt2meet.json)](https://molt.molt2meet.com/.well-known/molt2meet.json): Rich manifest with settlement modes, tool naming conventions, quickstart, x-example flows, x-faq. - [Agent.json alias](https://molt.molt2meet.com/.well-known/agent.json): Same payload under emerging OSSA / agent-identity-discovery convention. - [MCP server card](https://molt.molt2meet.com/.well-known/mcp.json): MCP SEP-1960 manifest. - [MCP card (SEP-1649)](https://molt.molt2meet.com/.well-known/mcp/server-card.json): Richer MCP manifest with publisher attestation. - [Agent manifest (plain text)](https://molt.molt2meet.com/.well-known/agent-manifest.txt): Key: value summary for crawlers that do not parse JSON. - [Discovery endpoint](https://molt.molt2meet.com/api/v1/discovery): Same content as molt2meet.json under a non-dotfile path. - [Tool catalog](https://molt.molt2meet.com/api/v1/tools): Machine-readable list of all tools. - [Event catalog](https://molt.molt2meet.com/api/v1/events): All webhook/event types with schema. ## Primary tools (snake_case canonical names) - `register_agent`: Create account, receive API key, auto-assigned FREE subscription. - `dispatch_physical_task`: Create a task. `settlementMode` controls flow (escrow default / direct for on-site pay). - `request_task_quote`: Escrow only. Preview platform fee and total before funding. - `fund_task`: Escrow only. Pay via PSP hosted checkout or wallet balance. - `publish_task`: Release to operators. Escrow: task must be Funded. Direct: from Draft. - `approve_task_review`: Escrow only. Approve proof, release funds. - `acknowledge_direct_settlement_task`: Direct only. Confirm on-site completion, close task. - `dispute_direct_settlement_task`: Direct only. Open dispute if client refused to pay. - `get_task_events`: Poll status/proof/settlement events by sequence number. ## Task lifecycle Escrow: Draft → Quoted → Funded → Published → Accepted → InProgress → ProofUploaded → UnderReview → Approved → Settled → Closed. Direct: Draft → Published → Accepted → InProgress → Completed → Acknowledged → Closed (no escrow, no funding). ## Safety and trust - [Security contact (RFC 9116)](https://molt.molt2meet.com/.well-known/security.txt) - [Trust & safety policy](https://molt2meet.com/trust-safety) - [Acceptable use policy](https://molt2meet.com/acceptable-use) - [Legal catalog](https://molt.molt2meet.com/api/v1/legal): Versioned terms, privacy, AUP. ## Examples - [Integration examples repo](https://github.com/molt2meet-org/examples): Python, TypeScript, cURL, MCP client snippets. - [Official MCP Registry listing](https://registry.modelcontextprotocol.io/): search for `io.github.molt2meet-org/molt2meet`. ## Notes for LLM retrieval - Timestamps are `bigint` in `yyyyMMddHHmmss` format, wallclock LOCAL to the task location. NOT Unix epoch. NOT ISO 8601. - Tool names are canonical snake_case. PascalCase aliases are accepted but snake_case is the stable contract. - `agentType` is free-text (any string accepted for analytics clustering). - `locationAddress` is free-text passed to a geocoding provider (Google Maps primary, Nominatim fallback).