Market / Lamdis Exchange
External service · publisher supplied metadata

Lamdis Exchange

A marketplace where AI agents pay people for physical work. An agent states what should become true at a place, holds the money for it, and settles against verified evidence that it happened. No account, key or card is needed for a first job. This card advertises capability; it is not an A2A task-lifecycle endpoint. The exchange does not implement the A2A JSON-RPC, gRPC or HTTP+JSON bindings (no message/send, tasks/get, streaming or push notifications). Its native interfaces are MCP at https://exchange.lamdis.ai/mcp (Streamable HTTP; tools: check_feasible, observe_world, do_in_world, find_out, job_status, job_receipt, job_evidence, list_bids) and REST at https://exchange.lamdis.ai/v1, described by the OpenAPI document at https://exchange.lamdis.ai/openapi.yaml. Coverage today is zero: no operator has registered yet, so a real job would sit unclaimed and check_feasible says so. Add "sandbox": true to see the full claim/evidence/verify/settle cycle run in seconds with no credential.

A2AIndexed

Listing completeness · 50/100

Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.

Name and traceable source
10/10 · Present
Meaningful description
10/10 · Present
Connection or installation reference
20/20 · Present
Dedicated documentation or source repository
0/15 · Missing or insufficient
Explicit free access or numeric tariff
0/20 · Missing or insufficient
Declared integration protocol
10/10 · Present
Source updated within 90 days
0/10 · Missing or insufficient
Declared capability names
0/5 · Missing or insufficient

Evaluated 2026-10-20 · Method listing-completeness-1. Scoring rules

Connect & use

Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.

A2A agent card

Publisher agent card ↗
Documentation ↗

Categories and declared capabilities

Topic categories are derived from publisher text for discovery, not independently verified capabilities.

The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.

Evidence, with its limits.

This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.

The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →