Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey13 EndpointsREST
For Agents
Programmatically verify authentication, list contact fields. Covers 13 operations with apiKey authentication.
Use for: I need to verify authentication, I want to contact fields, Search for a contact, Find all contacts
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
Plezi is a marketing automation platform. The API provides access to contacts, events, subscriptions, and contact lists. The API exposes 13 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Plezi API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Plezi 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.
1
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%2Fplezi.co%2Fplezi" | sh2
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%2Fplezi.co%2Fplezi" | 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.
Capabilities
What an agent can do with Plezi API.
Verify authentication
List contact fields
Create a contact
Export all contacts
Get recently updated contacts
Filter contacts by behavior score
Use Cases
Patterns agents use Plezi API for, with concrete tasks.
★ Payments Operations
Use the Plezi API to perform payments operations programmatically. The API provides 13 endpoints covering core functionality including verify authentication, list contact fields, create a contact.
Call GET / to verify authentication
Automated Authentication Management
Automate authentication operations by combining multiple Plezi API endpoints. Agents can list contact fields and then create a contact in a single workflow.
Call GET /settings/contact_fields to list contact fields, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Plezi 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 'verify authentication', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — plezi is a marketing automation platform.
METHOD
PATH
DESCRIPTION
GET
/
Verify authentication
GET
/settings/contact_fields
List contact fields
POST
/contacts
Create a contact
GET
/contacts
List contacts
GET
/export_all_contacts
Export all contacts
GET
/contacts_updated
Get recently updated contacts
GET
/contacts_updated_by_score
Filter contacts by behavior score
GET
/subscriptions
Export subscriptions
GET
/
Verify authentication
GET
/settings/contact_fields
List contact fields
POST
/contacts
Create a contact
GET
/contacts
List contacts
GET
/export_all_contacts
Export all contacts
GET
/contacts_updated
Get recently updated contacts
GET
/contacts_updated_by_score
Filter contacts by behavior score
GET
/subscriptions
Export subscriptions
Jentic AI Readiness Score
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.
P
Plezi API
- AI-Aware (B)66/100
93
Foundational Compliance63
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
36%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Plezi API by hand means handling its API key auth against app.plezi.co, then managing contact pagination and update polling yourself. Through Jentic you install once, import the Plezi API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Plezi's contact operations take their filters and payloads in the request body rather than pinning a record in the URL path, so scope the agent to the operations it needs, such as creating a contact or listing contacts. You choose that set, so a write like contact creation is included only if you add it while a read-only agent keeps just the list and export operations.
Credential isolation
Your Plezi 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 'create a contact' or 'export all contacts', and Jentic returns the matching Plezi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
FAQs
Specific to using Plezi API through Jentic.
What authentication does the Plezi API use?
The Plezi 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 verify authentication with the Plezi API?
Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Plezi 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 verify authentication through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verify authentication'. Jentic returns the matching Plezi API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Plezi API have?
The Plezi API exposes 13 endpoints covering authentication, contact lists, contacts operations.
Can I limit what my agent is allowed to do with the Plezi API?
Yes. Because you run Jentic One yourself, your own rules decide which Plezi operations and credentials the agent may use. Since Plezi's contact operations take their filters and payloads in the request body rather than pinning a record in the URL path, you scope the agent to just the operations it needs, such as listing contacts and exporting all contacts for a read-only agent. A write like creating a contact is available only if you add that operation to the agent's allowed set.
GET STARTED