Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Montonio Stargate Payments 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%2Fmontonio.com%2Fmontonio" | 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%2Fmontonio.com%2Fmontonio" | 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 Montonio Stargate Payments API.
Create a payment order and retrieve its status
Draft and finalize a payment intent
Issue a refund against an order
Retrieve the payment methods available to a store
Submit a hire-purchase application for Buy Now Pay Later financing
GET STARTED
Retrieve payouts recorded for an order
Patterns agents use Montonio Stargate Payments API for, with concrete tasks.
★ AI agent checkout via Jentic
An AI agent connected through Jentic takes a payment without wiring Montonio's auth by hand. It searches by intent such as creating a payment order, Jentic returns the matching Montonio operation with its input schema, and the agent creates the order and reads its status. The developer's own Jentic One instance injects the bearer token at call time.
Call POST /orders to create a payment order, then GET /orders/{order_uuid} to read its status
Payment intents flow
Checkouts that need an interim step draft a payment intent before completing it. Montonio drafts a payment intent, retrieves it, and finalizes it, so an agent can stage a payment, present methods, and finalize once the shopper confirms.
Call POST /payment-intents/draft to stage a payment, then POST /payment-intents/{intent_uuid}/finalize to complete it
Refunds and payouts reconciliation
Merchants reverse charges and reconcile settlement. Montonio issues a refund against an order and retrieves the payouts recorded for an order, so an agent can process a return and match the resulting payout back to the original order.
Call POST /orders/{order_uuid}/refunds to refund an order, then GET /orders/{order_uuid}/payouts to reconcile payouts
Buy Now Pay Later financing
Stores offer installment financing at checkout. Montonio creates a hire-purchase application and retrieves its status, so an agent can submit a BNPL application for a shopper and track whether the financing was approved.
Call POST /hire-purchase/applications to submit a BNPL application, then GET /hire-purchase/applications/{application_uuid} for its status
10 endpoints — the montonio stargate payments api lets merchants create and manage payments through an estonian payment gateway serving the baltics and europe.
METHOD
PATH
DESCRIPTION
/orders
Create a payment order
/orders/{order_uuid}
Retrieve an order
/orders/{order_uuid}/refunds
Create a refund for an order
/payment-intents/draft
Draft a payment intent
/payment-intents/{intent_uuid}/finalize
Finalize a payment intent
/stores/setup
Retrieve available payment methods
/hire-purchase/applications
Create a hire purchase application
/orders/{order_uuid}/payouts
Retrieve payouts for an order
/orders
Create a payment order
/orders/{order_uuid}
Retrieve an order
/orders/{order_uuid}/refunds
Create a refund for an order
/payment-intents/draft
Draft a payment intent
/payment-intents/{intent_uuid}/finalize
Finalize a payment intent
/stores/setup
Retrieve available payment methods
/hire-purchase/applications
Create a hire purchase application
/orders/{order_uuid}/payouts
Retrieve payouts for an order
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Montonio Stargate Payments API by hand means learning its bearer scheme, switching between the sandbox and production hosts, and sequencing the draft-and-finalize payment intent flow yourself. Through Jentic you install once, import Montonio from the API Directory, store the token once, and your agent calls the order and payment operations.
Permission scoping
Montonio puts the order and intent ids in the URL path (/orders/{order_uuid}, /payment-intents/{intent_uuid}), so a rule can pin your agent to one order and the read side of it. You choose the operations it may call, so issuing refunds or finalizing payment intents are not included unless you add them.
Credential isolation
Your Montonio bearer token 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 payment order' or 'issue a refund', and Jentic returns the matching Montonio 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.
Specific to using Montonio Stargate Payments API through Jentic.
What authentication does the Montonio Stargate Payments API use?
The Montonio Stargate Payments API authenticates with an HTTP bearer token in the Authorization header, per its OpenAPI spec, and offers a sandbox host alongside production. Through Jentic, your token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.
Can I create payment orders and refunds with the Montonio Stargate Payments API?
Yes. The order operations create a payment order, retrieve its status, and issue a refund against it, and the store setup operation returns the payment methods available for the order. An agent can take a payment and reverse it through the same gateway.
What are the rate limits for the Montonio Stargate Payments API?
The OpenAPI spec does not state numeric rate limits. Check the Montonio documentation at https://docs.montonio.com for current limits, and test against the sandbox host before going live.
How do I create a payment order through Jentic?
Search Jentic by intent such as creating a payment order, and it returns the Montonio order-create operation with its input schema. Create the order, present the available methods, and read the order status, with your token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Montonio Stargate Payments API?
Yes. Montonio puts the order id in the URL path, such as /orders/{order_uuid}, so a rule can pin your agent to one order and allow only reading its status and payouts. State-changing operations such as issuing a refund or finalizing a payment intent stay out unless you add them, and every call is logged by your self-hosted instance.
Is there a Montonio Stargate Payments API MCP server?
You do not need an MCP server to give your agent the Montonio Stargate Payments API. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent calls the order and payment-intent operations on demand without loading another server's tool definitions into its context.
For Agents
Create payment orders and intents, issue refunds, retrieve available payment methods, and submit hire-purchase (BNPL) applications through the Montonio gateway.
Use for: I need to create a payment order, I want to issue a refund for an order, Draft a payment intent for a checkout, Finalize a payment intent
Not supported: Does not handle accounting, tax filing, or subscription billing. Use for payment orders, refunds, and Buy Now Pay Later financing only.
The Montonio Stargate Payments API lets merchants create and manage payments through an Estonian payment gateway serving the Baltics and Europe. It creates payment orders, drafts and finalizes payment intents, issues refunds, and retrieves available payment methods for a store. It supports bank payments, card payments, Buy Now Pay Later financing through hire-purchase applications, and local payment methods, and offers a sandbox host alongside production.
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>