Provided by RentCast
Look Up One Long-Term Rental Listing by Its RentCast ID
Look up a single long-term rental listing by the RentCast id that the rental search returns, and get back the full listing: address, property type, bedrooms, bathrooms, square footage, year built, HOA fee, monthly rent, status, the date it was listed and removed, days on market, MLS name and number, the listing agent and office with their phone and email, and the rent history of the listing. The id is case-sensitive and comes from another RentCast call.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the RentCast endpoint /listings/rental/long-term/{id} on Glasser.glasser run -p rentcast -e '/listings/rental/long-term/{id}' -i '{"id":"2005-Arborside-Dr,-Austin,-TX-78754"}' --endpoint-version 1Uses endpoint version 1. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"rentcast","endpoint":"/listings/rental/long-term/{id}","input":{"id":"2005-Arborside-Dr,-Austin,-TX-78754"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to assess a location, you might compare its available place or property details with the requirements for your project.
Copy this prompt into your agent to review a location against your requirements.
Use rentcast:/listings/rental/long-term/{id} on Glasser.
Check the returned place or property details against my location requirements.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^[^/?]+,-[A-Z]{2}-\\d{5}$",
"maxLength": 200,
"minLength": 12
}
},
"additionalProperties": false
}{
"id": "2005-Arborside-Dr,-Austin,-TX-78754"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Data returned | Charged only when data is returned. | $0.0814 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |