PropEco Flood Risk API

Name: PropEco Flood Risk API
Brand: PropEco Flood Risk API
Availability: InStock

✓ Official Vendor SpecMaps GeolocationMappingapiKey1 EndpointsREST

For Agents

Programmatically get flood risk data. Covers 1 operations with apiKey authentication.

Install Jentic One Beta

Connect the PropEco Flood Risk API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PropEco Flood Risk API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpropeco.io%2Fpropeco" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpropeco.io%2Fpropeco" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PropEco Flood Risk API.

Get flood risk data

Access PropEco Flood Risk API resources via REST API

Use Cases

GET STARTED

Start building with PropEco Flood Risk API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query PropEco Flood Risk API endpoints to retrieve structured data for monitoring, reporting, or downstream processing. The API returns JSON responses that agents can parse directly, enabling automated data collection workflows without manual intervention.

Query the PropEco Flood Risk API API to retrieve current data and verify the response contains expected fields

AI Agent Integration via Jentic

AI agents discover and call PropEco Flood Risk API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'get flood risk data', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — retrieves flood risk information for uk properties and locations, including risk assessments for england, scotland, and wales, elevation data, coastal proximity, flood defences, and historical flood events.

METHOD

PATH

DESCRIPTION

GET

/flood-risk

Get flood risk data

GET

/flood-risk

Get flood risk data

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the PropEco Flood Risk API by hand means passing your key in the x-api-key header and parsing its flood-risk response yourself. Through Jentic you install once, import PropEco from the API Directory, store the key once, and your agent calls it.

Permission scoping

The PropEco Flood Risk API exposes a single read operation (GET /flood-risk) with no resource id in the path, so you limit the agent to the operations it needs, such as retrieving flood risk for a location. That read is the whole surface, and you decide it is the only thing the agent may call.

Credential isolation

Your PropEco Flood Risk API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get flood risk for an address', and Jentic returns the matching PropEco operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PropEco Flood Risk API through Jentic.

What authentication does the PropEco Flood Risk API use?

The PropEco Flood Risk API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I get flood risk data with the PropEco Flood Risk API?

Yes. Use the GET /flood-risk endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PropEco Flood Risk API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I get flood risk data through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get flood risk data'. Jentic returns the matching PropEco Flood Risk API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the PropEco Flood Risk API have?

The PropEco Flood Risk API exposes 1 endpoints covering flood risk operations.

Can I limit what my agent is allowed to do with the PropEco Flood Risk API?

Yes. Jentic One is self-hosted, so you run it and your own rules decide which operations and credentials the agent may use. The PropEco Flood Risk API exposes a single read operation, GET /flood-risk, with no resource id in the path, so you can allow only that call for retrieving flood risk at a location and nothing else. Since that read is the entire surface, the agent can query flood risk data but cannot reach any operation you have not permitted.

PropEco Flood Risk API

Connect the PropEco Flood Risk API to your agent

Capabilities

Use Cases

Start building with PropEco Flood Risk API

Key Endpoints

Why Jentic?

Related APIs

FAQs