Skip to content

Proquiro for developers & AI agents

Proquiro Developer Resources

Proquiro publishes a complete agent-ready surface — an MCP server with land-acquisition calculators, an OpenAPI 3.0 spec for the public API, RFC 9727 API Catalog, an Agent Skills index, llms.txt, and markdown content negotiation on every HTML page. Use the sections below to wire Proquiro into agents, copilots, and downstream tooling.

Proquiro MCP Server

The Proquiro MCP server speaks JSON-RPC 2.0 over Streamable HTTP and exposes 6 land-acquisition calculator tools that AI agents can call directly. MCP clients (Claude Desktop, Cursor, custom agents) can discover the server through its server card and stream tool calls without screen-scraping. Send Accept: application/json, text/event-stream on the handshake to opt into SSE responses.

Endpoint
POST https://proquiro.com/mcp
Protocol version
2025-06-18
Transport
Streamable HTTP — JSON or SSE on the same URL, CORS-enabled, batch-aware
Session header
Mcp-Session-Id issued on first response; pass it back on subsequent requests
Server name
proquiro-land-tools v1.0.0
Methods
initialize, ping, tools/list, tools/call

Tools exposed by the Proquiro MCP server

  • land_area_convert — Convert a land area value between Indian land measurement units (sqft, sqm, sqyd, acre, hectare, cent, ground, guntha, biswa, bigha, kanal, marla, katha, dismil, ankanam).
  • price_per_sqft — Calculate price per square foot, square meter, and price per the supplied unit for a land parcel.
  • land_roi — Calculate land investment return: total profit, total ROI, and annualized ROI.
  • guideline_value_check — Compare government guideline value (circle rate / jantri / ready reckoner) against market rate. Returns market premium percentage.
  • land_acquisition_cost — Calculate full land acquisition cost including stamp duty, registration, brokerage, legal fees, and other costs.
  • proquiro_roi — Estimate annual ROI of replacing manual land acquisition coordination with Proquiro.

Quick test from the command line

curl -sS https://proquiro.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Proquiro Public API

The Proquiro Public API is intentionally narrow — it covers form-handler and health endpoints for the marketing site. It is not a general-purpose data API for the hosted Proquiro app. All endpoints are rate-limited per IP, honeypot-protected, and reject disposable email domains.

  • POST /api/demo-request — submit a demo request (5 req/IP/hr)
  • GET /api/health — service health (returns { status })

Markdown reference: /api/docs.

Proquiro OpenAPI Spec

The full OpenAPI 3.0 specification for the Proquiro Public API is published as a static, CORS-enabled JSON document with the canonical application/openapi+json media type so SDK generators and AI tooling can consume it directly.

Catalog
/.well-known/api-catalog  (RFC 9727 application/linkset+json)

Agent authentication

The Proquiro public API and MCP server are unauthenticated and rely on per-IP rate limiting plus agent User-Agent identification. For higher-volume access or hosted-app data, partner Bearer tokens are issued on request. The full step-by-step guide lives at /developers/auth — Proquiro Agent Authentication Guide.

Streaming & SSE

Long-running and progress-bearing operations stream over Server-Sent Events (SSE) using HTTP chunked transfer. The Proquiro MCP server implements the MCP Streamable HTTP transport: clients negotiate streaming with the Accept header on the same /mcp URL — no separate SSE endpoint, no WebSocket.

  • Send Accept: text/event-stream on POST to receive each JSON-RPC response as an SSE message event with chunked transfer encoding
  • Send Accept: text/event-stream on GET to open a long-lived stream for server-pushed notifications (notifications/ready, notifications/cancelled, etc.)
  • Heartbeats are emitted as SSE comments (: keep-alive) so intermediaries don't drop idle connections
  • Sessions persist across requests via the Mcp-Session-Id response header — pass it back on subsequent calls

SSE handshake example:

curl -sSN https://proquiro.com/mcp \
  -H 'accept: application/json, text/event-stream' \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-06-18","capabilities":{},
                 "clientInfo":{"name":"AcmeAgent","version":"1.0"}}}'

For non-MCP endpoints, all current Proquiro public APIs are short-lived and return a single JSON document — streaming isn't required. New endpoints that introduce long-running operations (batch document verification, multi-step pricing walkthroughs) will be added under /api/stream/* and documented here.

JSON error schema

Every Proquiro public API endpoint returns a structured JSON error on failure — never an HTML error page. Agents can branch on a stable error.code without parsing prose. All error responses set Content-Type: application/json and CORS headers. 

{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Too many requests from this network. Please try again later.",
    "hint": "Limit: 5 requests per IP per hour.",
    "docs": "https://proquiro.com/developers#proquiro-public-api"
  }
}

Stable error codes:

  • INVALID_PAYLOAD — request body wasn't valid JSON / wrong method (HTTP 400 / 405)
  • MISSING_FIELDS — a required field was empty (HTTP 400)
  • INVALID_EMAIL — email failed format validation (HTTP 400)
  • DISPOSABLE_EMAIL — email belongs to a known disposable provider (HTTP 400)
  • HONEYPOT_TRIGGERED — the website field was non-empty (HTTP 400)
  • RATE_LIMITED — IP exceeded the per-hour limit. Honor Retry-After (HTTP 429)
  • DUPLICATE_REQUEST — the (email, tool) tuple was already submitted (HTTP 409)
  • DB_NOT_CONFIGURED, DB_NOT_INITIALIZED, INTERNAL_ERROR — server-side issues. Retry with exponential backoff (HTTP 500)

MCP errors are returned as standard JSON-RPC 2.0 error objects with codes -32700 (Parse error), -32601 (Method not found), and -32602 (Invalid params).

Proquiro Agent Skills Index

The Agent Skills index is a machine-readable catalogue of every agent-callable resource Proquiro publishes — calculators, checklists, the MCP server, and reference data — each with a SHA-256 digest so agents can detect changes.

/.well-known/agent-skills/index.json

Free agent-callable land tools (also in the index): Land Area Unit Converter, Price Per Sq Ft Calculator, Land ROI Calculator, Guideline Value Checker, Land Acquisition Cost Calculator, plus due-diligence, site visit, document-readiness, and title-risk checklists under /tools.

Proquiro llms.txt

llms.txt is the canonical entry point for AI crawlers. It links every public Proquiro surface — product pages, free tools, the blog, glossary, MCP server, OpenAPI spec, and discovery endpoints — in a deterministic order.

/llms.txt

Crawl rules and content signals are declared in /robots.txt. The XML sitemap index lives at /sitemap-index.xml.

Markdown content negotiation

Every HTML page on proquiro.com can be requested as Markdown by sending an Accept: text/markdown header. The response uses Content-Type: text/markdown with an X-Markdown-Tokens token-count hint so agents can budget context windows. 

curl -sS https://proquiro.com/blog \
  -H 'accept: text/markdown'

Blog posts also support a static .md suffix (e.g. /blog/encumbrance-certificate-verification-india.md) for cache-friendly fetches.

Questions or partner integrations

For integration questions, higher-volume API access, or co-development on agent workflows, write to info@proquiro.com or use the contact form. AI-governance and policy questions go to ai@proquiro.com; see also the Proquiro AI Policy.