ResidentPrints Developer Resources

    Machine-readable entry points for developers and AI agents integrating with the ResidentPrints managed printer amenity: the public API, the MCP server, and the conventions they follow.

    APIs and machine-readable files

    • OpenAPI 3.1 specification

      https://www.residentprints.com/openapi.json

      The machine-readable description of the ResidentPrints public REST API: request a property proposal, send a contact message, and discovery endpoints. Every operation has a unique operationId, typed schemas, and documented error responses.

    • MCP server

      https://www.residentprints.com/mcp

      A Model Context Protocol server over Streamable HTTP with no authentication required. Tools: check_service_coverage, get_pricing_model, list_solutions, get_company_overview, and request_property_proposal. Resources mirror the FAQ, pricing model, service area, and this API's OpenAPI spec.

    • MCP manifest

      https://www.residentprints.com/.well-known/mcp.json

      Discovery document for the MCP server: endpoint URL, transport, protocol version, and capabilities.

    • llms.txt

      https://www.residentprints.com/llms.txt

      A curated markdown map of the whole site in llmstxt.org format, including when-to-use guidance for AI assistants.

    • Sitemap

      https://www.residentprints.com/sitemap.xml

      Every indexable page, sharded at 5,000 URLs per file.

    API conventions

    Markdown content negotiation
    Every public marketing page returns a markdown rendition when requested with an Accept: text/markdown header, with Vary: Accept set on both variants.
    Structured JSON errors
    API endpoints return errors as { "error": { "code", "message", "hint", "docs" } } — never HTML error pages. Unknown API paths return this shape with HTTP 404.
    Real 404s
    Nonexistent paths return HTTP 404 with recovery links (and a markdown body for markdown negotiators), never a 200 app shell.
    Rate limits
    Public contact endpoints are limited to 5 requests per 15 minutes per IP; 429 responses include a Retry-After header.

    Authentication

    The endpoints above are public and need no credentials. Resident and property-management APIs are cookie-authenticated through the dashboard and are not part of the public integration surface — if you need programmatic access to them, contact the team.