For Developers and Third-Party Apps
You're building software — a sustainability platform, an asset-management tool, or an AI agent — that needs real-estate sustainability data. SDX gives you two ways in, both free:
- REST API — for traditional server-to-server integrations.
- MCP server — for AI agents (Claude, Cursor, your own) that need to read and write SDX data through tool calls.
There are no integration fees, no per-call charges, and no licensing costs for reading or writing on behalf of owners.
Your first run
- Read the API overview.
- Run the 5-minute quickstart.
- Set up authentication — scoped API keys, bcrypt-hashed, instantly revocable.
- Write data on behalf of an owner using the sandbox.
- Wire SDX into your AI agent through the MCP server.
Topics for developers
- API vs. MCP: which to use — the decision tree
- API quickstart
- Authentication and scoped keys — 11 permission scopes, request only what you need
- Reading data on behalf of owners
- Writing data on behalf of owners
- Code examples — Python, JavaScript, cURL, Ruby
- Sandbox environment
- Rate limits and error responses
- Webhooks
- OpenAPI spec
MCP server
The MCP server is the right path for AI agents. It exposes SDX as tool calls a model can invoke directly — no glue code in your app. Connect it to Claude Desktop, Cursor, or any MCP-compatible client. See /mcp for connection instructions.
On-behalf-of permissions
Every API key and MCP session acts on behalf of a specific owner organization. The owner controls what your integration can do — read-only, operate, or full management — and can revoke access at any time. Your code does not bypass that model; it operates inside it.
Still stuck?
Email the team. We read every message in the beta.