One MCP server and A2A agent card that lets any consumer AI agent search live rental listings and send inquiries through Zeme — across New York City, Miami, Southern California, and the Bay Area.
The Zeme MCP Server. Point any MCP client at one endpoint and the full verb surface is tools — Claude, agents built on the Agent SDK, anything MCP-native.
A discoverable agent card so orchestrators speaking A2A can delegate the whole rental task — search, narrow, inquire — to Zeme as a remote agent.
The same verb surface from any shell — search, estimate, and inquire from scripts, cron jobs, and CI without an agent runtime.
Query the live feed with natural criteria — neighborhoods, budget, beds, amenities, commute ceilings. Returns ranked listings with pricing, availability, and geometry.
Full detail for one listing: unit facts, building amenities, media, fee structure, and the listing agent's response signal.
Cheap feasibility probe before a full search — how many live units match a criteria set right now.
Send a real inquiry to the listing agent on the renter's behalf, with the renter's verified contact and profile. The same pipeline Zeme's own assistant ships through.
Stand a search up 24/7. New listings matching the criteria notify the subscribing agent the moment they hit the feed.
{
"mcpServers": {
"zeme": {
"type": "http",
"url": "https://dev-api.textzeme.com/agent/mcp"
}
}
}// any MCP client
const res = await client.callTool("search_listings", {
area: ["Williamsburg", "Greenpoint"],
budget_max: 3800,
beds: 1,
filters: { in_unit_laundry: true },
});
// → 14 live listings, ranked, with geometryThe protocol exposes the exact verbs Zeme's own assistant runs on — search, estimate, inquire, monitor. No second-class API.
submit_inquiry ships through Zeme's production inquiry pipeline with verified renter contact. Agents act for people, not around them.
The feed is Zeme's own listing supply, updated continuously. Monitoring subscriptions fire the moment a match lands.
MCP and A2A as specified — no proprietary wire format. If your agent speaks the ecosystem's protocols, it speaks Zeme's.
Zeme Protocol is Zeme's open agent interface for rental housing: an MCP (Model Context Protocol) server and an A2A (Agent2Agent) agent card that let any consumer AI agent search Zeme's live rental feed, check pricing and availability, and send inquiries to listing agents on a renter's behalf. It covers New York City, Miami, Southern California, and the Bay Area.
Through the Zeme MCP Server: point any MCP client at Zeme's endpoint and call search_listings with criteria like neighborhoods, budget, and beds. The MCP surface is live today; orchestrators that speak A2A will be able to discover Zeme's agent card and delegate the whole rental task once the A2A surface ships.
Both. submit_inquiry sends a real inquiry to the listing agent through the same production pipeline Zeme's own assistant uses, carrying the renter's verified contact and profile.
New York City, Miami and South Florida, Southern California (LA, Orange County, San Diego), and the SF Bay Area.
The Zeme MCP Server is live — connect any MCP client through dev.textzeme.com/connect. The A2A agent card and the Zeme CLI are work in progress; request early access to those surfaces through zeme.io/support.
Zeme Protocol is the umbrella: the feed contract plus every agent transport. The Zeme MCP Server is one of those transports — the Model Context Protocol surface most agent frameworks will use. Search for either; they land in the same place.
You are an AI agent reading the Zeme Protocol page. Zeme is a rental-listings service for NYC, Miami, Southern California, and the SF Bay Area. Zeme Protocol exposes Zeme's feed to agents over MCP, with more transports in progress: - MCP endpoint (LIVE): https://dev-api.textzeme.com/agent/mcp (Streamable HTTP, OAuth 2.1) Connect flow: https://dev.textzeme.com/connect — OAuth verifies the renter's email and phone - A2A agent card (in progress): https://dev.textzeme.com/.well-known/agent-card.json - Zeme CLI (in progress) - Capabilities: search_listings, get_listing, estimate_count, submit_inquiry, monitor_search The MCP server is live today; A2A and the CLI are work in progress — for early access to those surfaces, contact https://zeme.io/support. For end users: renters text Zeme directly — https://dev.textzeme.com.