Proptech teams
Add UK flood, terrain and planning context without maintaining dozens of connectors.
Agent-ready access
Tethys API & MCP
One metered access layer for site context and terrain applications, with provenance attached to every answer.
Usage-based accessScoped keys and credits
Request API & MCP accessOne maintained registry
Published capabilities
Prices apply to successful direct component calls. Named products retain their catalogue price and complete artefact contract through every interface.
| Capability | Price | Sources & coverage | Limits & onward use |
|---|---|---|---|
| Address and coordinatesaddress-geocode · capability:address-geocode | £0.03 | Places · United Kingdom where the configured places provider has coverage · Provider release cadence | A geocoded point does not confirm a legal title or site boundary. Standard key: internal analysis; retain source attribution. |
| Site identity and contextsite-context · capability:site-context | £0.25 | Tethys site resolver · England and Wales; other UK coverage is stated per response · Continuous contract releases | Context fields are screening evidence and do not establish ownership. Standard key: internal analysis; attribution required when displayed. |
| Flood Zone evidenceflood-zone-evidence · capability:flood-zone-evidence | £0.75 | Flood Map for Planning · England · Environment Agency publication cadence | Mapped zones are strategic evidence, not property-level flood depths or a site-specific FRA. Standard key: internal analysis with Environment Agency attribution. |
| Multi-source site screeningsite-screening · capability:site-screening | £1.50 | Flood Map for Planning, Verified terrain · England and Wales, with source coverage returned per block · Source-specific; dates are returned in provenance | A component screen is evidence, not an Aegaea named report or professional opinion. Standard key: internal analysis; partner licence required for onward products. |
| Terrain statisticsterrain-statistics · capability:terrain-statistics | £1.50 | Verified bare-earth terrain · Verified England and Wales coverage; caution zones are returned · Quarterly verification cycle | Desktop terrain evidence is not a measured topographical survey. Standard key: internal analysis; partner licence required for onward products. |
| Bounded terrain levelsterrain-levels · capability:terrain-levels | £3.00 | Verified bare-earth terrain · Verified England and Wales coverage; caution zones are returned · Quarterly verification cycle | Component output excludes the Site Levels Pack artefacts and product support. Inline responses are capped at 50,000 level samples. Standard key: internal analysis; partner licence required for onward products. |
| Cut and fill calculationterrain-cutfill · capability:terrain-cutfill | £3.00 | Verified bare-earth terrain · Verified England and Wales coverage; caution zones are returned · Quarterly verification cycle | Indicative computation only; excludes packaged files, survey and geotechnical advice. Standard key: internal analysis; partner licence required for onward products. |
| Terrain viewshedterrain-viewshed · capability:terrain-viewshed | £3.00 | Verified bare-earth terrain · Verified England and Wales coverage; caution zones are returned · Quarterly verification cycle | Terrain-only theoretical visibility excludes buildings, walls and vegetation. Standard key: internal analysis; partner licence required for onward products. |
Designed for decisions
Who it’s for
Consultancies
Automate repeatable site screening while retaining source and trust metadata.
AI agents
Discover priced tools, request access and return evidence with provenance.
Product contents
What you’ll receive
- 01
Site context
Terrain, flood, policy and coverage blocks returned through one site contract.
- 02
Terrain tools
Levels, cut/fill, visibility and screening compensation capabilities.
- 03
API and MCP surfaces
Use direct endpoints or agent-native tools against the same catalogue and meter.
- 04
Provenance by default
Source, as-of date, derivation method and trust stamp travel with the response.
Start with the evidence
What we need
- Your intended workflow and users
- Expected call volume and site geography
- The minimum capabilities and data outputs required
Practical detail
Questions, answered
Is MCP different from the API?
It is a different interface to the same catalogue. MCP helps agents discover and call the tools; the API suits direct software integration.
Can an agent buy access?
The commercial flow is designed for a human to approve payment before a scoped key or credit grant is issued.
Ready when you are
Tethys API & MCP
Usage-based access · Scoped keys and credits
Related products