Retrieve a specific US rental listing by its RentCast ID, paid per call via MPP/Tempo.
What it does
This endpoint returns detailed information about a single US rental listing given its RentCast listing ID. It is one of several RentCast endpoints exposed through the Locus MPP (Micropayment Protocol) gateway, which wraps the RentCast API with per-call crypto payments settled on Tempo L2 using pathUSD.
The endpoint accepts a POST request with a JSON body containing a required `id` field (the RentCast rental listing ID). Each call costs 33,000 base units of pathUSD (6 decimals), which equals $0.033 per request. Payment is handled automatically via the MPP 402 challenge-response flow — no API key or subscription is needed; the agent simply settles the micropayment on each call.
This endpoint is part of a broader RentCast suite available on the same gateway, which includes property records lookup, AVM value estimates, rent estimates, sale listings, rental listings search, and market statistics by zip code. The upstream data comes from RentCast (rentcast.io), a US real estate data provider. Note that the probe returned 404 on HEAD/GET for this specific path, which is expected since the endpoint only accepts POST requests as defined in the OpenAPI spec. No response schema is documented, so the exact shape of the returned rental listing object is not confirmed from the probe material alone — refer to the upstream RentCast API reference for field details.
Capabilities
Use cases
- —Fetching full details of a specific rental listing when you already have its RentCast ID
- —Enriching a rental property pipeline with listing-level data (price, photos, description)
- —Building a rental comparison tool that drills into individual listings
- —Agent-driven workflows that need on-demand rental listing details without API key management
Fit
Best for
- —AI agents that need pay-per-call access to US rental listing data
- —Developers building rental market analysis tools
- —Workflows that already have RentCast listing IDs from a prior search call
Not for
- —Bulk downloading all rental listings in a market (use the rental-listings search endpoint instead)
- —Non-US property data
- —Users who need a free or subscription-based pricing model
Quick start
curl -X POST https://rentcast.mpp.paywithlocus.com/rentcast/rental-listing-by-id \
-H "Content-Type: application/json" \
-d '{"id": "some-rental-listing-id"}'Example
Request
{
"id": "5500-Grand-Lake-Dr-Unit-3-San-Antonio-TX-78244"
}Endpoint
Quality
The OpenAPI spec provides a clear request schema and pricing info, but there is no response schema documented, no example responses, and the probe did not capture a 402 challenge on this specific endpoint (expected since it only accepts POST). Upstream RentCast docs are referenced but not crawled.
Warnings
- —Probe returned 404 on HEAD/GET — endpoint only accepts POST, so this is expected behavior, not an outage signal.
- —No response schema is provided in the OpenAPI spec; the shape of the returned rental listing object is unknown from available material.
- —The example request ID is fabricated for illustration; actual valid listing IDs must be obtained from the /rentcast/rental-listings search endpoint.
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo/Locus convention; if decimals differ, the price would change.
Citations
- —Endpoint path, POST method, required 'id' field, and payment amount of 33000 base units via Tempohttps://rentcast.mpp.paywithlocus.com
- —RentCast provides US real estate intelligence including property records, AVM valuations, rent estimates, sale/rental listings, and market statisticshttps://rentcast.io
- —Upstream API reference available at developers.rentcast.iohttps://developers.rentcast.io/reference/introduction
- —LLM-oriented docs for this MPP service at beta.paywithlocus.comhttps://beta.paywithlocus.com/mpp/rentcast.md