Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Subscriptions, 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%2Fpaypal.com%2Fsubscriptions" | 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%2Fpaypal.com%2Fsubscriptions" | 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 Subscriptions API.
Create plan
List plans
Show plan details
Update plan
Activate plan
GET STARTED
Deactivate plan
Patterns agents use Subscriptions API for, with concrete tasks.
★ Payments Operations
Use the Subscriptions to perform payments operations programmatically. The API provides 16 endpoints covering core functionality including create plan, list plans, show plan details.
Call POST /v1/billing/plans to create plan
Automated plans Management
Automate plans operations by combining multiple Subscriptions endpoints. Agents can list plans and then show plan details in a single workflow.
Call GET /v1/billing/plans to list plans, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Subscriptions 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 oauth2 tokens manually.
Search Jentic for 'create plan', load the operation schema, and execute with Jentic-managed credentials
16 endpoints — you can use billing plans and subscriptions to create subscriptions that process recurring paypal payments for physical or digital goods, or services.
METHOD
PATH
DESCRIPTION
/v1/billing/plans
Create plan
/v1/billing/plans
List plans
/v1/billing/plans/{id}
Show plan details
/v1/billing/plans/{id}
Update plan
/v1/billing/plans/{id}/activate
Activate plan
/v1/billing/plans/{id}/deactivate
Deactivate plan
/v1/billing/plans/{id}/update-pricing-schemes
Update pricing
/v1/billing/subscriptions
Create subscription
/v1/billing/plans
Create plan
/v1/billing/plans
List plans
/v1/billing/plans/{id}
Show plan details
/v1/billing/plans/{id}
Update plan
/v1/billing/plans/{id}/activate
Activate plan
/v1/billing/plans/{id}/deactivate
Deactivate plan
/v1/billing/plans/{id}/update-pricing-schemes
Update pricing
/v1/billing/subscriptions
Create subscription
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PayPal Subscriptions by hand means running its OAuth 2.0 flow, refreshing Bearer tokens, and choosing the right sandbox or live host before you can manage billing plans and subscriptions. Through Jentic you install once, import Subscriptions from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
Subscriptions puts the plan id in the URL path (/v1/billing/plans/{id}), so a rule can pin your agent to reading one billing plan. You choose the operations it may call, so activating, deactivating, or updating a plan's pricing is not included unless you add them.
Credential isolation
Your PayPal OAuth client id and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time, with token refresh handled for you. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a billing plan' or 'create a subscription', and Jentic returns the matching Subscriptions 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 Subscriptions API through Jentic.
What authentication does the Subscriptions use?
The Subscriptions uses OAuth 2.0 for authorization. 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 plan with the Subscriptions?
Yes. Use the POST /v1/billing/plans endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Subscriptions?
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 plan through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create plan'. Jentic returns the matching Subscriptions operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Subscriptions have?
The Subscriptions exposes 16 endpoints covering plans, subscriptions, subscriptions-buyer-consent operations.
Can I limit what my agent is allowed to do with the PayPal Subscriptions API?
Yes. Because Jentic One is self-hosted, your own rules decide which of the Subscriptions operations the agent may call, so you can grant read-only access with GET /v1/billing/plans and GET /v1/billing/plans/{id} while withholding create, update, activate, and deactivate. Since the plan id sits in the URL path (/v1/billing/plans/{id}), a rule can pin the agent to a single billing plan rather than the whole account. Write actions such as POST /v1/billing/plans, the activate and deactivate calls, update-pricing-schemes, and creating subscriptions stay blocked until you explicitly add them, and the OAuth client credentials are injected by your instance so the agent never sees the raw secrets.
For Agents
Programmatically create plan, list plans. Covers 16 operations with oauth2 authentication.
Use for: I need to plan, I want to plans, Search for show plan details, Find all plan
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
You can use billing plans and subscriptions to create subscriptions that process recurring PayPal payments for physical or digital goods, or services. A plan includes pricing and billing cycle information that defines the amount and frequency of charge for a subscription. You can also define a fixed plan, such as a $5 basic plan or a volume- or graduated-based plan with pricing tiers based on the . The API exposes 16 endpoints secured with oauth2 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>