Look up a US property record by RentCast ID, paid per call via MPP/Tempo.
What it does
This endpoint retrieves a single US property record from RentCast by its unique property ID. It is one of several RentCast endpoints exposed through the Locus MPP (Micropayment Protocol) gateway. You supply a RentCast property ID (formatted like "5500-Grand-Lake-Dr,-San-Antonio,-TX-78244") and receive the corresponding property record in return.
The endpoint is part of a broader RentCast suite available on the same gateway, which includes property search, AVM value estimates, rent estimates, sale and rental listings, and market statistics. Each call costs 33,000 base units of pathUSD on Tempo L2, which equals $0.033 per request (pathUSD uses 6 decimals). Payment is handled via the MPP charge intent — each call is a one-shot micropayment settled on Tempo.
Note: The probe returned 404 on HEAD and GET, which is expected because this endpoint only accepts POST requests as specified in the OpenAPI schema. The OpenAPI spec is well-defined with a clear request schema. However, no response schema or example response is documented, so the exact shape of returned property data must be inferred from RentCast's own API reference.
Capabilities
Use cases
- —Retrieve full property details for a known RentCast property ID
- —Enrich a CRM or investment pipeline with property attributes after initial search
- —Power automated property analysis workflows that already have RentCast IDs from prior queries
- —Build property comparison tools that fetch individual records on demand
Fit
Best for
- —Agents or apps that already have a RentCast property ID and need the full record
- —Programmatic real estate data retrieval with per-call micropayments
- —Workflows combining this with the sibling /rentcast/properties search endpoint
Not for
- —Bulk property searches by location or criteria (use the /rentcast/properties endpoint instead)
- —Non-US property data
- —Users who need free or subscription-based access without per-call crypto payments
Quick start
curl -X POST https://rentcast.mpp.paywithlocus.com/rentcast/property-by-id \
-H "Content-Type: application/json" \
-d '{"id": "5500-Grand-Lake-Dr,-San-Antonio,-TX-78244"}'Example
Request
{
"id": "5500-Grand-Lake-Dr,-San-Antonio,-TX-78244"
}Endpoint
Quality
The OpenAPI schema is clear with a well-defined request body and payment info, but no response schema or example response is provided. The probe returned 404 because HEAD/GET were used while the endpoint only accepts POST. Crawl pages returned no useful documentation. Price is clearly derivable from the OpenAPI spec.
Warnings
- —No response schema documented — the shape of the returned property record is unknown from this source alone
- —Probe did not confirm a live 402 challenge because only HEAD and GET were attempted; the endpoint requires POST
- —No example responses available in the OpenAPI spec or crawl bundle
- —The currency address 0x20c000000000000000000000b9537d11c60e8b50 is assumed to be pathUSD with 6 decimals based on the Tempo/Locus convention; this is not explicitly confirmed in the probe
Citations
- —The endpoint accepts POST with a required 'id' field as the RentCast property IDhttps://rentcast.mpp.paywithlocus.com
- —Each call costs 33,000 base units via Tempo charge intenthttps://rentcast.mpp.paywithlocus.com
- —RentCast provides US real estate intelligence including property records, AVM valuations, rent estimates, sale/rental listings, and market statisticshttps://rentcast.mpp.paywithlocus.com
- —API reference available at developers.rentcast.iohttps://developers.rentcast.io/reference/introduction
- —LLM-readable docs at beta.paywithlocus.com/mpp/rentcast.mdhttps://beta.paywithlocus.com/mpp/rentcast.md