Agency Developer Access
Understand client API credentials, delegated products, team roles and approved AI connections.
Use developer access to build custom experiences for an agency client. Each client keeps its own purchased plan, approved website, product access and credentials.
Client API requirements
- The client needs active paid Pro or Brokerage service.
- The client website must be verified and have active MLS approval.
- API access and the required products must be delegated to that client.
- The key must be issued for the client website with scopes permitted by the purchased plan, delegated products and issuing user's role.
A separate client key keeps requests within that client's account and approved website. Store its secret on your server and use its public X-EAI-Site-ID value on every request. Follow API authentication for headers, credential storage and rotation.
Client workspace summaries
An agency credential with the client workspace capability and clients:read scope can call GET /api/v1/platform/clients. It returns up to 100 client workspace summaries, including the client's plan, status, delegated API products and resource totals. This is an agency account resource rather than a normal customer capability.
Use GET /api/v1/platform/capabilities to check the current key's operations and scopes. Workspace summaries do not authorize requests to another client's leads or listing feed. Use that client's own authorized credentials for its resources.
Usage limits
Client API limits follow the client's purchased plan on each approved website. A new key does not create another allowance. Review API rate limits and the rate headers returned with each response.
Home Valuations access
A client needs the delegated ahv product, an active Home Valuations subscription for the selected website and the appropriate valuations:read or valuations:write scope. Website verification and MLS approval still apply. Follow the Valuations API for requests and credit handling.
Agency team roles
Agency accounts can invite team members, including a Developer role. That role covers developer tools, sites, analytics and read access to widgets. Owners and authorized Admins issue keys that access private customer records or change resources. Roles do not expand the client's purchased plan or delegated products.
AI connections through MCP
An agency-managed client needs delegated API access, an eligible paid plan and a verified website with an active approved MLS feed. The person connecting must use their own authorized customer login and select the permitted website and information. The connection stays within that client's current role, products and API allowance. Follow AI connections through MCP for the connection steps.
MCP provides its documented read-only tools. Agency provisioning, billing and white-label controls are outside that tool set. A Demo Site does not grant paid client API access.