Install Jentic One Beta

Connect the Access PaySuite to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Access PaySuite, 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%2Fddcms.accesspaysuite.com%2Fddcms-accesspaysuite" | 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%2Fddcms.accesspaysuite.com%2Fddcms-accesspaysuite" | 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 Access PaySuite API.

Create and read customers and their Direct Debit contracts under a client

Set up and amend recurring payment schedules by frequency and amount

Freeze, skip, cancel, restart, or reactivate a contract's collection

Take one-off payments and submit bulk payment runs

Read a contract's schedules, future schedules, and payment history

GET STARTED

Start building with Access PaySuite API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Access PaySuite API for, with concrete tasks.

★ Agent-Managed Direct Debit Onboarding

An AI agent onboards a new payer by creating the customer under a client, opening a Direct Debit contract, and setting a monthly schedule in one flow. The agent reads the contract's future schedules back to confirm the first collection date, so a signup assistant can set up recurring billing end to end.

Create a customer under the client, open a Direct Debit contract, set a monthly schedule, and return the next collection date

Recurring Payment Adjustments

Handle mid-contract changes without manual intervention: change the collected amount, freeze a run of cycles, or skip the next payment when a payer asks. The API exposes dedicated patch actions for change-amount, freeze, and skip, so a support agent can apply the right adjustment and log it against the contract.

Freeze the next two collection cycles on a contract, then read its future schedules to confirm the change

Bulk Collection Runs

Collect from many contracts at once by submitting a bulk payment run for a client, then reconcile the results against each contract's payment history. This drives scheduled billing jobs that would otherwise call the single-payment endpoint repeatedly.

Submit a bulk payment run for the client and then read each contract's payment history to confirm the collections

Key Endpoints

46 endpoints — the access paysuite api manages uk direct debit and bacs collection for a client: you create customers, set up recurring payment contracts, and run the schedules that collect from them.

METHOD

PATH

DESCRIPTION

GET

/client/{clientCode}/customer

List customers for a client

POST

/client/{clientCode}/customer

Create a customer

POST

/client/{clientCode}/customer/{customerId}/contract

Open a Direct Debit contract for a customer

POST

/client/{clientCode}/contract/{contractId}/payment

Take a one-off payment on a contract

GET

/client/{clientCode}/contract/{contractId}/schedule

Read a contract's schedule

POST

/client/{clientCode}/contract/{contractId}/patch/freeze

Freeze collection cycles

POST

/client/{clientCode}/bulk/payments

Submit a bulk payment run

GET

/client/{clientCode}/schedules

List schedules across the client

GET

/client/{clientCode}/customer

List customers for a client

POST

/client/{clientCode}/customer

Create a customer

POST

/client/{clientCode}/customer/{customerId}/contract

Open a Direct Debit contract for a customer

POST

/client/{clientCode}/contract/{contractId}/payment

Take a one-off payment on a contract

GET

/client/{clientCode}/contract/{contractId}/schedule

Read a contract's schedule

POST

/client/{clientCode}/contract/{contractId}/patch/freeze

Freeze collection cycles

POST

/client/{clientCode}/bulk/payments

Submit a bulk payment run

Why Jentic?

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

Setup

By hand you provision an API key, set the apiKey header, learn the client, contract, and schedule model, and wire the patch actions for amount, freeze, and skip before collecting a payment. Through Jentic you connect once from the API Directory and your agent calls the operations by intent.

Permission scoping

The client code and contract id travel in the URL path, so a rule can bind the agent to a single client's contracts. You grant only the operations it needs, for example reading schedules and taking payments while withholding cancellations, and every call is logged.

Credential isolation

Your API key is stored encrypted on your own Jentic One instance and injected into the apiKey header at execution time, never placed in the agent's prompt, logs, or context. You rotate or revoke it in one place without touching agent code.

Intent-based discovery

Agents search Jentic by intent such as 'open a Direct Debit contract' or 'take a payment', and Jentic returns the matching Access PaySuite operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Access PaySuite API through Jentic.

What authentication does the Access PaySuite API use?

The spec declares an apiKey scheme that sends your key in an apiKey header, so every request carries that key. Through Jentic, your own Jentic One instance stores the key encrypted and attaches it to each call rather than exposing it to the agent.

Can I pause or change a Direct Debit after it is set up?

Yes. Each contract has dedicated actions to change the amount, switch frequency, freeze a run of cycles, skip the next payment, cancel, restart, or reactivate. You read the contract's future schedules afterwards to confirm the change took effect.

What are the rate limits for the Access PaySuite API?

The OpenAPI spec does not state rate limits. Check the official Access PaySuite documentation at https://developer.accesspaysuite.com/ for current limits before running large bulk payment jobs.

How do I collect Direct Debits through Jentic?

Add the Access PaySuite API from the Jentic API Directory and connect your key once. Your agent then searches by intent such as 'open a Direct Debit contract' and calls the matching operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I restrict which Access PaySuite operations my agent is allowed to call?

Yes. The client code and contract id travel in the URL path, so a rule can bind the agent to a single client's contracts and allow only the operations it needs, such as reading schedules while withholding payment collection. Every call the agent makes is logged.

Is there an Access PaySuite MCP server?

You don't need an MCP server to use Access PaySuite with your agent. Jentic connects it directly from the API Directory: import it, connect your key once, and your agent can create contracts and take payments without another server loading tool definitions into its context.

Ddcms Accesspaysuite Access PaySuite

AI ReadinessNon-Ready (F)38/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsBilling SubscriptionsapiKey46 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create customers and recurring Direct Debit contracts, run and amend their payment schedules, and take one-off or bulk BACS payments through Access PaySuite. Reads schedules, future schedules, and payment history per contract.

Use for: Create a new customer and Direct Debit contract, Set up a monthly payment schedule for a contract, I want to freeze a customer's payments for two cycles, Take a one-off payment on a contract

Not supported: Does not handle card payments, invoicing, or general-ledger accounting. Use for UK Direct Debit and BACS collection through Access PaySuite only.

The Access PaySuite API manages UK Direct Debit and BACS collection for a client: you create customers, set up recurring payment contracts, and run the schedules that collect from them. You amend a contract's amount or frequency, freeze or skip cycles, take one-off and bulk payments, and read the schedules, future schedules, and payment history for any contract. BACS callbacks and client questions round out the workflow around onboarding and collecting recurring payments.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D-Signals: 4

69%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

19%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

48%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

51%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

18%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Access PaySuite to your agent

Capabilities

Start building with Access PaySuite API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ddcms Accesspaysuite Access PaySuite

Jentic AI Readiness Score

Access Paysuite

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness