Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SiPay Wallet 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%2Fsipay.com.tr%2Fsipay-com-tr" | 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%2Fsipay.com.tr%2Fsipay-com-tr" | 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 SiPay Wallet API.
Create payment
Manage payments data programmatically
Integrate SiPay Wallet API into automated workflows
Query and filter SiPay Wallet API records by parameters
Monitor SiPay Wallet API operational status and events
GET STARTED
Patterns agents use SiPay Wallet API for, with concrete tasks.
★ Payments Operations
Use the SiPay Wallet API to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including create payment.
Call POST /v1/Transaction/Payment to create payment
Data Retrieval and Monitoring
Query SiPay Wallet API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary SiPay Wallet API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call SiPay Wallet 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 'create payment', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — sts api for sipay wallet payment transactions.
METHOD
PATH
DESCRIPTION
/v1/Transaction/Payment
Create payment
/v1/Transaction/Payment
Create payment
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SiPay Wallet API by hand means setting up its key in the Authorization header and threading it through the payment call on the walletapi host yourself. Through Jentic you install once, import SiPay Wallet from the API Directory, store the key once, and your agent calls it.
Permission scoping
The SiPay Wallet API carries the payment details in the request body rather than as a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as submitting a payment, and leave any other operations out unless you add them.
Credential isolation
Your SiPay Wallet 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 'take a wallet payment', and Jentic returns the matching SiPay Wallet 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 SiPay Wallet API through Jentic.
What authentication does the SiPay Wallet API use?
The SiPay Wallet API uses an API key passed 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 payment with the SiPay Wallet API?
Yes. Use the POST /v1/Transaction/Payment endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SiPay Wallet 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 payment through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create payment'. Jentic returns the matching SiPay Wallet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SiPay Wallet API have?
The SiPay Wallet API exposes 1 endpoints covering transactions operations.
Can I limit what my agent is allowed to do with the SiPay Wallet API?
Yes. Because Jentic One is self-hosted by you, your own rules decide which SiPay Wallet API operations and credentials the agent may use. Since the SiPay Wallet API carries payment details in the request body rather than as a resource id in the URL path, you scope the agent by operations: grant only the calls it needs, such as submitting a payment through POST /v1/Transaction/Payment, and leave every other operation out unless you add it. Your stored API key is injected only for the operations you have allowed, so the agent can act on nothing you have not explicitly permitted.
For Agents
Programmatically create payment. Covers 1 operations with apiKey authentication.
Use for: I need to payment, Find available payments operations, Get the current status of SiPay Wallet API resources, List all records from SiPay Wallet API
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
STS API for SiPay wallet payment transactions. The API exposes 1 endpoints secured with apiKey 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>