Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pluggy Open Finance 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%2Fpluggy.ai%2Fpluggy" | shStep 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%2Fpluggy.ai%2Fpluggy" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Pluggy Open Finance API.
Create API key
List available connectors
Retrieve a specific connector
Validate connector credentials
Patterns agents use Pluggy Open Finance API for, with concrete tasks.
GET STARTED
★ Payments Operations
Use the Pluggy Open Finance API to perform payments operations programmatically. The API provides 36 endpoints covering core functionality including create API key, create connect token, list available connectors.
Call POST /auth to create API key
Automated Auth Management
Automate auth operations by combining multiple Pluggy Open Finance API endpoints. Agents can create connect token and then list available connectors in a single workflow.
Call POST /connect-token to create connect token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pluggy Open Finance 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 bearer tokens manually.
Search Jentic for 'create API key', load the operation schema, and execute with Jentic-managed credentials
36 endpoints — pluggy open finance api for connecting to financial institutions, managing items, accounts, transactions, investments, and webhooks.
METHOD
PATH
DESCRIPTION
/auth
Create API key
/connect-token
Create connect token
/connectors
List available connectors
/connectors/{id}
Retrieve a specific connector
/connectors/validate
Validate connector credentials
/items
Create a connection item
/items/{id}
Retrieve an item
/items/{id}
Update an item
/auth
Create API key
/connect-token
Create connect token
/connectors
List available connectors
/connectors/{id}
Retrieve a specific connector
/connectors/validate
Validate connector credentials
/items
Create a connection item
/items/{id}
Retrieve an item
/items/{id}
Update an item
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Pluggy Open Finance API by hand means exchanging your keys for a bearer token at /auth, managing connect tokens, and tracking each connection item yourself. Through Jentic you install once, import the Pluggy Open Finance API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Pluggy puts the item and connector id in the URL path (/items/{id}, /connectors/{id}), so a rule can pin your agent to one item: it can read and update that connection and nothing else. You choose the operations it may call, so creating new items is included only if you add the POST /items operation.
Credential isolation
Your Pluggy credential 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 'list available connectors' or 'read an item', and Jentic returns the matching Pluggy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using Pluggy Open Finance API through Jentic.
What authentication does the Pluggy Open Finance API use?
The Pluggy Open Finance API uses a Bearer token in the Authorization 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 create API key with the Pluggy Open Finance API?
Yes. Use the POST /auth endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pluggy Open Finance 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 create API key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create API key'. Jentic returns the matching Pluggy Open Finance API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Pluggy Open Finance API have?
The Pluggy Open Finance API exposes 36 endpoints covering auth, connectors, items operations.
Can I limit what my agent is allowed to do with the Pluggy Open Finance API?
Yes. Because Jentic One is self-hosted, you decide which Pluggy operations your agent may call and which credential it uses, so you can allow read and update on a connection while withholding creation. Since Pluggy carries the item and connector id in the URL path, such as /items/{id} and /connectors/{id}, a rule can pin the agent to a single item so it reads and updates that connection and nothing else. Creating new connections through POST /items is available only if you explicitly add that operation to the agent's allowed set.
For Agents
Programmatically create API key, create connect token. Covers 36 operations with bearer authentication.
Use for: I need to API key, I want to connect token, Search for available connectors, Find all a specific connector
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Pluggy open finance API for connecting to financial institutions, managing items, accounts, transactions, investments, and webhooks. The API exposes 36 endpoints secured with bearer authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>