Can I check API key authorization with the Rentometer API?

Yes. Use the GET /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Rentometer API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I check API key authorization through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check API key authorization'. Jentic returns the matching Rentometer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Rentometer API have?

The Rentometer API exposes 7 endpoints covering authentication, rent data, reports operations.

Can I limit what my agent is allowed to do with the Rentometer API?

Yes. Because you run Jentic One yourself, your own rules decide which Rentometer operations and credentials the agent may use, so you can allow only the read calls it needs, such as GET /summary for a rent summary, GET /nearby_comps for comparables, or GET /property_rents for property-level data. Rentometer passes its lookups as query parameters rather than resource ids in the path, so scoping is done per operation rather than per record. Costlier or write-style actions like GET /request_pro_report, GET /pro_report_status, and GET /download_pro_report stay off limits unless you explicitly add them. Your API key is injected at execution time and never enters the agent's prompt or context.