Install Jentic One Beta

Connect the Developer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Developer 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%2Fsqala.tech%2Fsqala-tech" | 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%2Fsqala.tech%2Fsqala-tech" | 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 Developer API.

Create an Access Token

List all Pix QR Codes

Retrieve a Pix QR Code

Query and filter Developer API records by parameters

Monitor Developer API operational status and events

GET STARTED

Start building with Developer API

Explore with Jentic One

View OpenAPI Document

Automated Recipient Management

Automate recipient operations by combining multiple Developer API endpoints. Agents can create a pix qr code and then list all pix qr codes in a single workflow.

Call POST /pix-qrcode-payments to create a pix qr code, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Developer 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 basic tokens manually.

Search Jentic for 'create an access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

28 endpoints — at sqala, we believe that everyone deserves access to financial services, and we are committed to providing secure and reliable payment solutions to clients who may have been overlooked by traditional financial institutions.

METHOD

PATH

DESCRIPTION

POST

/access-tokens

Create an Access Token

POST

/pix-qrcode-payments

Create a Pix QR Code

GET

/pix-qrcode-payments

List all Pix QR Codes

GET

/pix-qrcode-payments/{id}

Retrieve a Pix QR Code

POST

/itp-payments

Create an ITP

GET

/itp-payments

List all ITPs

GET

/itp-payments/{id}

Retrieve an ITP

POST

/boleto-payments

Create a Boleto

POST

/access-tokens

Create an Access Token

POST

/pix-qrcode-payments

Create a Pix QR Code

GET

/pix-qrcode-payments

List all Pix QR Codes

GET

/pix-qrcode-payments/{id}

Retrieve a Pix QR Code

POST

/itp-payments

Create an ITP

GET

/itp-payments

List all ITPs

GET

/itp-payments/{id}

Retrieve an ITP

POST

/boleto-payments

Create a Boleto

Why Jentic?

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

Setup

Wiring the Sqala Developer API by hand means handling its basic auth against api.sqala.tech/developer/v1 and minting access tokens before you can create Pix, ITP, or boleto payments. Through Jentic you install once, import the Developer API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

You can limit the agent to the operations it needs, such as reading a Pix QR-code payment by id or listing ITP payments, so it stays on the payment types you allow and never creates a boleto or ITP payment unless you add those operations.

Credential isolation

Your Sqala credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Pix QR-code payment' or 'check the status of a payment', and Jentic returns the matching Developer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Developer API through Jentic.

What authentication does the Developer API use?

The Developer API uses HTTP Basic authentication with username and password. 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 an access token with the Developer API?

Yes. Use the POST /access-tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Developer 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 an access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an access token'. Jentic returns the matching Developer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Developer API have?

The Developer API exposes 28 endpoints covering recipient, boleto, qrcode operations.

Can I limit what my agent is allowed to do with the Sqala Developer API?

Yes. Because you run Jentic One yourself, you decide which Sqala operations the agent may call, so you can allow read-only actions like retrieving a Pix QR-code payment by id or listing ITP payments while withholding anything else. If you never add the create operations, the agent cannot create a boleto or an ITP payment, and it stays on the payment types you approve. Your Sqala basic-auth credentials are stored encrypted by your own instance and injected only when an allowed call runs.

Sqala Tech Developer API

Name: Developer API
Brand: Developer API
Availability: InStock

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbasic28 EndpointsREST

For Agents

Programmatically create an access token, create a pix qr code. Covers 28 operations with basic authentication.

Use for: I need to an access token, I want to a pix qr code, Search for all pix qr codes, Find all a pix qr code

Not supported: Does not handle communications, crm, or developer tools - use for payments only.

At Sqala, we believe that everyone deserves access to financial services, and we are committed to providing secure and reliable payment solutions to clients who may have been overlooked by traditional financial institutions. The API exposes 28 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Connect the Developer API to your agent

Capabilities

Start building with Developer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sqala Tech Developer API