Sandbox Api Starkbank Stark Bank API

Name: Stark Bank API
Brand: Stark Bank API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingnone72 EndpointsREST

For Agents

Programmatically create transactions, list transactions. Covers 72 operations.

Use for: I need to transactions, I want to transactions, Search for transaction by id, Find all balances

Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.

Stark Bank API for financial services in Brazil. The API exposes 72 endpoints.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Stark Bank API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Stark Bank 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%2Fsandbox.api.starkbank.com%2Fsandbox-api-starkbank" | 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%2Fsandbox.api.starkbank.com%2Fsandbox-api-starkbank" | 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 Stark Bank API.

Create transactions

List transactions

Get transaction by ID

Query and filter Stark Bank API records by parameters

Monitor Stark Bank API operational status and events

GET STARTED

Start building with Stark Bank API

Explore with Jentic One

View OpenAPI Document

Automated invoice Management

Automate invoice operations by combining multiple Stark Bank API endpoints. Agents can list transactions and then get transaction by id in a single workflow.

Call GET /transaction to list transactions, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Stark Bank 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 none tokens manually.

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

Key Endpoints

72 endpoints — stark bank api for financial services in brazil.

METHOD

PATH

DESCRIPTION

POST

/transaction

Create transactions

GET

/transaction

List transactions

GET

/transaction/{transactionId}

Get transaction by ID

GET

/balance

List balances

POST

/transfer

Create transfers

GET

/transfer

List transfers

GET

/transfer/{transferId}

Get transfer by ID

GET

/transfer/{transferId}/pdf

Get transfer PDF receipt by ID

POST

/transaction

Create transactions

GET

/transaction

List transactions

GET

/transaction/{transactionId}

Get transaction by ID

GET

/balance

List balances

POST

/transfer

Create transfers

GET

/transfer

List transfers

GET

/transfer/{transferId}

Get transfer by ID

GET

/transfer/{transferId}/pdf

Get transfer PDF receipt by ID

Why Jentic?

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

Setup

Wiring the Stark Bank API by hand means building its request signing, choosing the sandbox or production api.starkbank.com host, and handling paging and retries across transfers and transactions yourself. Through Jentic you install once, import Stark Bank from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Stark Bank puts the resource id in the URL path (/transfer/{transferId}, /transaction/{transactionId}), so a rule can pin your agent to specific transfers and transactions: it can read the ones you allow and nothing else. You choose the operations it may call, so writes like creating transfers are not included unless you add them.

Credential isolation

Your Stark Bank 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 'get account balance' or 'get a transfer', and Jentic returns the matching Stark Bank operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Stark Bank API through Jentic.

What authentication does the Stark Bank API use?

The Stark Bank API uses no authentication. 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 transactions with the Stark Bank API?

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

What are the rate limits for the Stark Bank 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 transactions through Jentic?

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

How many endpoints does the Stark Bank API have?

The Stark Bank API exposes 72 endpoints covering invoice, boleto, brcodepayment operations.

Can I limit what my agent is allowed to do with the Stark Bank API?

Yes. Because you run Jentic One yourself, your own rules decide which Stark Bank operations and credentials the agent may use. Since Stark Bank puts the resource id in the URL path, such as /transfer/{transferId} and /transaction/{transactionId}, you can pin the agent to specific transfers and transactions and let it read only the ones you permit. You also choose the operations it may call, so write actions like POST /transfer to create transfers stay off unless you add them.

Sandbox Api Starkbank Stark Bank API

Connect the Stark Bank API to your agent

Capabilities

Start building with Stark Bank API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs