Rafid Property Intelligence

Property intelligence built for AI agents.
Discover. Pay per call. Execute.

MCP x402 ready REST (compatibility)

Agent Integration

Autonomous agents are the primary consumers of this API. The intended flow is: discover a capability, select the tool, pay per call over x402 (or authenticate with an API key), execute, get a structured machine-readable result.

MCP

Every tool is exposed over the Model Context Protocol with strict input/output schemas — run npm run mcp for a local stdio server.

x402 (pay-per-call)

No account, no API key. See /api/v1/x402 for terms and /api/v1/x402/status for live status.

OpenAPI

Full machine-readable spec with request/response examples at /openapi.json.

Agent manifest

Discovery documents at /agent.json, /.well-known/ai-plugin.json, /.well-known/agent.json and /llms.txt.

Pay per call, no wallet setup shown here

curl -X POST /api/v1/x402/property/analyze \
  -H "Content-Type: application/json" \
  -d '{"propertyValue":85000,"annualRent":7200,"serviceCharge":650,"maintenanceCost":400}'

Or authenticate with an API key

curl -X POST /api/v1/property/analyze \
  -H "X-API-Key: <your-key>" \
  -H "Content-Type: application/json" \
  -d '{"propertyValue":85000,"annualRent":7200,"serviceCharge":650,"maintenanceCost":400}'

Available tools

analyze_property Calculate gross/net rental yield, income, operating costs and simple payback in OMR. Calculations only. $0.01
compare_properties Compare 2–20 uniquely named properties in OMR using the same metrics; order by rounded net yield, preserving input order for ties. $0.03
estimate_maintenance Estimate an annual maintenance reserve in OMR from value, age and unit count with explicit optional assumptions. Uncalibrated heuristic, not a survey. $0.02
analyze_oman_property Analyze an Oman residential property using local rental comparables, market context and investment metrics. $0.25

Full capability registry — schemas, pricing, when to use each tool — at /api/v1/capabilities.

Access models

Two independent access models, never combined on one request: an X-API-Key header on /api/v1/..., or an unauthenticated /api/v1/x402/... call settled per call via the x402 protocol. Machine-readable pricing at /api/v1/pricing. Full REST reference: /openapi.json.

Developer documentation