Renterra agent & public resource documentation
Use this website to research Renterra equipment rental management software, compare its published features, and read customer stories. These resources describe the public marketing website, not an authenticated product API for managing rental accounts, inventory, contracts, or payments.
Public endpoints and authentication
These read-only resources need no sign-in, API key, or OAuth scope. The Renterra OpenAPI specification describes their operations and response types. It does not grant access to customer data.
- GET /llms.txt: when-to-use guidance and an index of published pages.
- GET /sitemap.xml: the XML index of published, indexable URLs.
- GET /robots.txt: the website's crawl policy.
Example requests
curl -sS https://getrenterra.com/llms.txt
curl -sS https://getrenterra.com/openapi.json
curl -sS -L -i -H 'Accept: text/markdown' https://getrenterra.com/does-not-exist
curl -sS -L -i -H 'Accept: application/problem+json' https://getrenterra.com/does-not-existMissing resources and errors
Missing resources return HTTP 404. Request text/markdown for a Markdown explanation, application/problem+json for an RFC 9457 problem detail, or application/json for the same JSON fields. JSON includes type, title, status, detail, instance, and the extensions code, resolution, and docs. Browser requests retain the HTML error page. Negotiated 404 responses include Vary: Accept and are not cached.
Product integrations and access
This website does not publish product API authentication instructions, permission scopes, a GraphQL schema, self-serve API keys, an SDK, an MCP server, or a sandbox. Do not treat the public website specification as evidence that those facilities are available. Read about Renterra integrations and contact Renterra to discuss your requirements. A person must handle demo requests and access arrangements; an agent should not submit forms or change account data without authorization.
Rate limits and responsible retrieval
No product API rate-limit or query-cost contract is published here. These static resources do not declare an API quota or guarantee rate-limit headers. Reuse retrieved documents and avoid repeated polling. If an upstream service returns HTTP 429 or 503 with Retry-After, wait for the indicated delay before retrying; otherwise use bounded exponential backoff. Confirm product API quotas and header conventions with Renterra before building an integration.