Retrieve a specific US for-sale property listing by its RentCast ID via pay-per-call MPP.
What it does
This endpoint returns details for a single for-sale property listing identified by its RentCast listing ID. It is one of several RentCast endpoints exposed through the Locus MPP (Micropayment Protocol) gateway, which wraps the RentCast real estate data API with per-call crypto payments settled on Tempo L2.
The request body accepts a single required field — `id` — which is the RentCast sale listing identifier. Each call costs $0.033 (33,000 base units of pathUSD with 6 decimals), charged via the MPP "charge" intent using the Tempo settlement method. The endpoint uses HTTP POST and returns listing data on successful payment.
This endpoint is part of a broader RentCast suite available at the same gateway, covering property records, AVM valuations, rent estimates, sale and rental listings, and market statistics — all at the same per-call price. The upstream data source is RentCast (rentcast.io), and full API reference documentation is available at developers.rentcast.io. Note that the probe returned 404 on HEAD/GET, which is expected since the endpoint only accepts POST requests as specified in the OpenAPI schema.
Capabilities
Use cases
- —Retrieve full details of a specific for-sale property listing when you already have its RentCast ID
- —Enrich a pipeline that discovered listing IDs via the sale-listings search endpoint
- —Power a property detail page in a real estate application
- —Validate or cross-reference listing data from another source against RentCast records
Fit
Best for
- —Agents or apps that need on-demand single-listing detail without a subscription
- —Programmatic real estate workflows that already use RentCast listing IDs
- —Developers who want crypto-settled pay-per-call access to US sale listing data
Not for
- —Bulk retrieval of many listings at once (use the sale-listings search endpoint instead)
- —Non-US property data
- —Users who need free or subscription-based access without per-call payments
Quick start
curl -X POST https://rentcast.mpp.paywithlocus.com/rentcast/sale-listing-by-id \
-H "Content-Type: application/json" \
-d '{"id": "your-sale-listing-id"}'Example
Request
{
"id": "5500-Grand-Lake-Dr-San-Antonio-TX-78244-sale"
}Endpoint
Quality
The OpenAPI schema is present with clear request body definition and pricing metadata, but the probe did not capture a live 402 challenge (only 404 on HEAD/GET, expected for a POST-only endpoint). No response schema or example response is documented. Crawled pages all returned generic 404 JSON, providing no additional documentation.
Warnings
- —Probe returned 404 on HEAD and GET — endpoint is POST-only; liveness not confirmed via 402 challenge on POST
- —No response schema documented in the OpenAPI spec; response structure must be inferred from upstream RentCast docs
- —Example response JSON is unavailable; the listing ID format is inferred from the property-by-id endpoint example
- —Currency address 0x20c000000000000000000000b9537d11c60e8b50 assumed to be pathUSD with 6 decimals based on Tempo/MPP conventions
Citations
- —The endpoint accepts POST with a required 'id' field and costs 33000 base units via Tempo settlementhttps://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
- —Full API reference documentation is available at developers.rentcast.iohttps://developers.rentcast.io/reference/introduction
- —LLM-oriented docs available at beta.paywithlocus.com/mpp/rentcast.mdhttps://beta.paywithlocus.com/mpp/rentcast.md