Install Jentic One Beta

Connect the UK Parliament Members API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UK Parliament Members 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%2Fparliament.uk%2Fmembers" | 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%2Fparliament.uk%2Fmembers" | 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 UK Parliament Members API.

Search for constituencies by name or location type

Retrieve constituency details including election results and geometry

Look up Members of Parliament by ID, name, or constituency

Get biographical information and party affiliations for MPs and Lords

Retrieve voting history and attendance records for individual members

GET STARTED

Start building with UK Parliament Members API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use UK Parliament Members API for, with concrete tasks.

★ Constituency Lookup and Representation

Find MPs representing specific geographic areas by searching constituencies by name or location type. GET /api/Location/Constituency/Search returns matching constituencies, then GET /api/Location/Constituency/{id}/Representations returns current and historical representatives. The API includes constituency boundaries via /Geometry endpoints for mapping applications.

GET /api/Location/Constituency/Search?searchText={area}, then GET /api/Location/Constituency/{id}/Representations to list MPs

Member Biography and Political Profile

Retrieve comprehensive biographical data, party affiliations, and parliamentary roles for MPs and Lords. Search by name via /api/Members/Search, then GET /api/Members/{id} returns full member details including house, party, constituency, and appointment dates. Cross-reference with /api/Members/{id}/Biography for extended background.

GET /api/Members/Search?Name={name}, then GET /api/Members/{id} and /api/Members/{id}/Biography for full profile

Voting Records and Parliamentary Activity

Access voting history, attendance, and parliamentary activity for individual members. The Voting endpoints return division lists and member vote records, while committee endpoints expose membership and roles across parliamentary committees and all-party parliamentary groups (APPGs).

GET /api/Members/{id}/Voting to retrieve voting history, GET /api/Members/{id}/RegisteredInterests for declared interests

AI-Powered Parliamentary Research via Jentic

An AI agent researching UK politics can search for members by party or constituency, retrieve voting patterns, cross-reference committee memberships, and pull declared interests through Jentic without managing pagination or session handling. Jentic resolves intents like 'find all Labour MPs' or 'get voting record for member X' to the correct Members API endpoints.

Search Jentic for 'find MPs by party', load GET /api/Members/Search schema with party filter, and execute

Key Endpoints

43 endpoints — jentic publishes the only agent-ready openapi specification for the uk parliament members api, keeping it validated and up to date.

METHOD

PATH

DESCRIPTION

GET

/api/Members/Search

Search for members by name, party, or house

GET

/api/Members/{id}

Retrieve detailed member information by ID

GET

/api/Location/Constituency/Search

Search constituencies by name

GET

/api/Location/Constituency/{id}/Representations

Get MPs representing a constituency

GET

/api/Location/Constituency/{id}/ElectionResults

Retrieve election results for a constituency

GET

/api/Members/{id}/Biography

Get extended biographical information

GET

/api/LordsInterests/Register

Access Lords register of interests

GET

/api/Members/Search

Search for members by name, party, or house

GET

/api/Members/{id}

Retrieve detailed member information by ID

GET

/api/Location/Constituency/Search

Search constituencies by name

GET

/api/Location/Constituency/{id}/Representations

Get MPs representing a constituency

GET

/api/Location/Constituency/{id}/ElectionResults

Retrieve election results for a constituency

GET

/api/Members/{id}/Biography

Get extended biographical information

GET

/api/LordsInterests/Register

Access Lords register of interests

Why Jentic?

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

Setup

Wiring the UK Parliament Members API by hand means pointing a client at its public host, shaping the member, constituency, and interests routes, and handling pagination and error states yourself. Through Jentic you install once, import the Members API from the API Directory, and your agent calls it with no credential to manage.

Permission scoping

The Members API puts the member and constituency id in the URL path (/api/Members/{id}, /api/Location/Constituency/{id}/...), so a rule can pin your agent to one member or constituency or to the read-only lookups. Since this public API only reads member data, the agent stays limited to retrieval.

Credential isolation

The Members API is open-access, so there is no credential to store; Jentic shapes the request and parses the response at execution time. No token ever enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find the MP for Bristol' or 'get the voting record for a member', and Jentic returns the matching Members operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using UK Parliament Members API through Jentic.

Is the UK Parliament Members API free to use?

Yes. The UK Parliament Members API is a public API with no authentication required and no rate limits published. It is maintained by UK Parliament's software engineering team and provides open access to parliamentary member data.

Can I get voting records for individual MPs?

Yes. Use GET /api/Members/{id}/Voting to retrieve voting history for a specific member, or search divisions to see how members voted on particular bills and motions. The API returns structured division voting data.

How do I find the MP for a specific constituency?

Use GET /api/Location/Constituency/Search with the constituency name to get the constituency ID, then GET /api/Location/Constituency/{id}/Representations to retrieve current and historical MPs representing that area.

Does this API include historical member data?

Yes. The Members API includes historical parliamentary data across sessions, including former MPs, previous party affiliations, and historical committee memberships. Filter by date ranges or session to access historical records.

Where does Jentic's OpenAPI spec for the Members API come from?

Jentic imports and validates the official Swagger spec published by UK Parliament at https://members-api.parliament.uk/swagger/v1/swagger.json, converts it to OpenAPI 3.0.3, and keeps it updated so AI agents and developers can call the API via structured tooling.

Can I search for members by party affiliation?

Yes. Use the GET /api/Members/Search endpoint with party filter parameters to retrieve all MPs and Lords from a specific political party. The API supports filtering by house, party, membership status, and name.

Can I limit what my agent is allowed to do with the UK Parliament Members API?

Yes. Because you run Jentic One self-hosted, your own rules decide which Members API operations your agent may call, so you can allow only read lookups such as GET /api/Members/Search and GET /api/Members/{id} and block anything else. Since the member and constituency id sit in the URL path (/api/Members/{id}, /api/Location/Constituency/{id}/Representations), a rule can pin the agent to a single member or constituency. This API is read-only and needs no credential, so the agent stays limited to retrieving member, constituency, voting, and interests data and can never modify it.

UK Parliament Members API

Name: UK Parliament Members API
Brand: UK Parliament Members API
Availability: InStock

Browse all Parliament Uk APIs

Identity AuthDirectory Servicesnone43 EndpointsREST

For Agents

Query UK MPs and Lords by name, constituency, or party; retrieve voting records, committee memberships, interests, and biographical data across 43 endpoints.

Use for: Who is the MP for a specific constituency?, Find all Conservative MPs in the House of Commons, Get the voting record for a particular member, List all committees that an MP serves on

Not supported: Covers member biographical data, constituencies, voting, and interests. Does not include bill text, Hansard transcripts, or detailed debate proceedings - use Bills, Hansard, or Commons/Lords Votes APIs for those.

Jentic publishes the only agent-ready OpenAPI specification for the UK Parliament Members API, keeping it validated and up to date. The Members API exposes comprehensive data about UK Members of Parliament and Members of the House of Lords, including biographical information, party affiliations, constituencies, voting records, committee memberships, declared interests, and historical parliamentary roles. It powers research platforms, civic tech applications, and political data analysis across current and historical parliamentary sessions.

Jentic One on Github View OpenAPI Document