# RICS (Royal Institution of Chartered Surveyors) > The British royal-chartered professional body, founded in London in 1868, that qualifies, > regulates and sets standards for surveyors, valuers and built-environment professionals > worldwide. RICS sits on the professional and valuation side of the property value chain, not the > listings side: it writes the Red Book (RICS Valuation – Global Standards, incorporating IVS), the > Home Survey Standard, RICS Property Measurement (IPMS), ICMS, ILMS and the Rules of Conduct, and > it regulates roughly 12,000 RICS-regulated firms. Because the United Kingdom has no MLS, there is > no RESO layer here at all — no RESO Web API, no Data Dictionary certification, no OData > $metadata, no Universal Property Identifier. RICS publishes two genuinely machine-readable things and no developer portal. The RICS Data Standard (RDS) 3.3.3 is an MIT-licensed JSON Schema and XSD on GitHub, downloadable anonymously. The DigitalCommunity API at api.rics.org serves its OpenAPI 3.0.1 contract publicly — but it is a regulation, membership, billing and survey-writer integration API, not a property-data API, and RICS must issue you a username and password before you can call it. There is no self-serve signup, no pricing page and no API documentation beyond the Swagger UI. Generated by API Evangelist on 2026-07-26. No /llms.txt is published by RICS; www.rics.org sits behind an Imperva Incapsula challenge that returns the same 212-byte body for every path. ## APIs - [RICS DigitalCommunity API](https://api.rics.org/): Live REST API, 16 operations across seven tags (Token, Profile, Regulation, Payment, SurveyWriter, AzureStorage, OlaMerchantPost). Covers firm regulation schemes, PII and redress declarations, subscriptions and licence seats, quotes, sales orders and payment requests, member profiles, and survey-writer licence validation. Bearer JWT from POST /token, credentials issued by RICS. Base URL https://api.rics.org ## Specs - [DigitalCommunity OpenAPI 3.0.1](https://api.rics.org/swagger/v1/swagger.json): the live contract, served anonymously (HTTP 200, 67,992 bytes). Harvested verbatim to openapi/rics-digitalcommunity-api-openapi.json - [RICS Data Standard 3.3.3 JSON Schema](https://github.com/RICS-Data-Standard/RDS): draft-04 JSON Schema for land, property, real estate and infrastructure assets, incorporating ICMS, ILMS, IPMS, IVS and IBOS, with address formats from buildingSMART IFC and OASIS xAL. MIT licensed. - [RICS Data Standard 3.3.3 XSD](https://github.com/RICS-Data-Standard/RDS): the same standard as a W3C XML Schema. - [Azure AD B2C OpenID Connect discovery](https://b2clogin.rics.org/ricsb2clive.onmicrosoft.com/B2C_1A_RICS_signup_signin/v2.0/.well-known/openid-configuration): RICS member sign-in. scopes_supported is ["openid"] only; this does not govern api.rics.org. ## Standards RICS publishes - [RICS Standards and Guidance](https://www.rics.org/profession-standards/rics-standards-and-guidance) - [RICS Valuation – Global Standards (Red Book)](https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/valuation-standards/red-book) - [RICS Property Measurement, 2nd edition (IPMS)](https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/real-estate-standards/rics-property-measurement-2nd-edition) - [RICS Data Standards](https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/construction-standards/rics-data-standards) ## Docs and properties - [RICS](https://www.rics.org/) - [About RICS](https://www.rics.org/about-rics) - [Regulation](https://www.rics.org/regulation): how RICS regulates members and firms - [Find a Surveyor](https://www.ricsfirms.com/): public directory of RICS-regulated firms, no API - [isurv](https://www.isurv.com/): subscription knowledge platform carrying the standards - [RICS Tech Partner Programme](https://www.rics.org/get-involved/rics-tech-partner-programme): the only published route to a RICS technology integration - [News and insights](https://www.rics.org/news-insights) - [Contact RICS](https://www.rics.org/footer/contact-us) - [Join fees](https://www.rics.org/join-rics/join-fees) - [Professional fees](https://www.rics.org/renew-my-membership/professional-fees) - [Terms and conditions](https://www.rics.org/footer/rics-org-terms-and-conditions) - [Privacy policy](https://www.rics.org/footer/rics-privacy-policy) - [RICS Data Standard on GitHub](https://github.com/RICS-Data-Standard/RDS) - [myRICS community](https://community.rics.org/home) ## API Evangelist artifacts in this repository - authentication/rics-authentication.yml: the single Bearer scheme - scopes/rics-scopes.yml: the one OIDC scope RICS advertises, and why the API has none - conventions/rics-conventions.yml: no idempotency, no pagination, no rate-limit signalling - errors/rics-problem-types.yml: the ProblemDetails envelope and every declared status - data-model/rics-data-model.yml: the 52-schema regulation entity graph - lifecycle/rics-lifecycle.yml: unversioned v1, no deprecation policy, no status page - changelog/rics-changelog.yml: the RDS GitHub release history (last release March 2022) - conformance/rics-conformance.yml: what RICS conforms to, and the RESO absence - well-known/rics-well-known.yml: every /.well-known/ probe and its status - security/rics-domain-security.yml: TLS, HSTS, DNSSEC, CAA, SPF and DMARC posture - mcp/rics-mcp.yml and mcp/rics-tool-crosswalk.yml: candidate tools derived from the OpenAPI - overlays/rics-digitalcommunity-api-overlay.yaml: the operationIds the spec never declared - agentic-access/rics-agentic-access.yml: recommended x-agentic-access contracts per operation - skills/: three grounded agent skills for the read paths ## What does not exist - No developer portal, no getting-started guide, no API reference beyond the Swagger UI. - No self-serve signup, no API pricing, no published rate limits, no SLA, no status page. - No SDKs or client libraries in any registry, and no CLI. - No sandbox, no test credentials, no test keys — the only test signal is the isTest flag on a payment request. - No webhooks, no events, no AsyncAPI, no GraphQL, no gRPC, no MCP server. - No security.txt, no vulnerability disclosure programme, no bug bounty, no trust centre and no published certifications. - No RESO Data Dictionary or Web API certification, and no open property dataset — the UK's open property data layer belongs to HM Land Registry and Ordnance Survey, not to RICS.