Install Jentic One Beta

Connect the API TSP to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API TSP, 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%2Fswaggerhub.tsp7%2Fapi-tsp" | 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%2Fswaggerhub.tsp7%2Fapi-tsp" | 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 API TSP API.

boletosFinanciado

dadosContrato

detalhesDivida

downloadBoleto

geraNegociacao

Use Cases

Patterns agents use API TSP API for, with concrete tasks.

GET STARTED

Start building with API TSP API

Explore with Jentic One

View OpenAPI Document

Automated Validação Management

Automate validação operations by combining multiple API TSP endpoints. Agents can dadoscontrato and then detalhesdivida in a single workflow.

Call GET /contrato/{id_financiado} to dadoscontrato, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API TSP 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 'boletosfinanciado', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — esta é a documentação da api tsp.

METHOD

PATH

DESCRIPTION

GET

/boletos_financiado/{id_financiado}

boletosFinanciado

GET

/contrato/{id_financiado}

dadosContrato

GET

/detalhes_divida/{id_contrato}

detalhesDivida

GET

/detalhes_divida_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}

detalhesDividaParelado

GET

/download_boleto/{id_boleto}

downloadBoleto

GET

/gera_negociacao/{opcao}/{id_contrato}

geraNegociacao

GET

/gera_negociacao_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}

geraNegociacaoParcelada

GET

/listagem_quebras/{cpf}

listagemQuebras

GET

/boletos_financiado/{id_financiado}

boletosFinanciado

GET

/contrato/{id_financiado}

dadosContrato

GET

/detalhes_divida/{id_contrato}

detalhesDivida

GET

/detalhes_divida_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}

detalhesDividaParelado

GET

/download_boleto/{id_boleto}

downloadBoleto

GET

/gera_negociacao/{opcao}/{id_contrato}

geraNegociacao

GET

/gera_negociacao_parcelado/{id_contrato}/{qntd_parcelas}/{valor_entrada}

geraNegociacaoParcelada

GET

/listagem_quebras/{cpf}

listagemQuebras

Why Jentic?

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

Setup

Wiring the API TSP by hand means pointing at its tsprecuperadora.com.br host and building your own retries across the contract, boleto, and negotiation endpoints, even though it exposes no auth scheme. Through Jentic you install once, import API TSP from the API Directory, store the connection details once, and your agent calls it.

Permission scoping

API TSP puts the contract and financed-party ids in the URL path (/contrato/{id_financiado}, /detalhes_divida/{id_contrato}), so a rule can pin your agent to one contract: it can read that contract's debt details and boletos and nothing else. Because you pick the allowed operations, the agent only runs the reads and negotiations you authorize.

Credential isolation

Any connection details for API TSP 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 a contract's boletos' or 'get debt details for a contract', and Jentic returns the matching API TSP operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API TSP API through Jentic.

What authentication does the API TSP use?

The API TSP 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 boletosfinanciado with the API TSP?

Yes. Use the GET /boletos_financiado/{id_financiado} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API TSP?

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 boletosfinanciado through Jentic?

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

How many endpoints does the API TSP have?

The API TSP exposes 11 endpoints covering validação, dados, negociação operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which API TSP operations and connection details your agent may use. API TSP carries the contract and financed-party ids in the URL path, such as /contrato/{id_financiado} and /detalhes_divida/{id_contrato}, so a rule can pin the agent to a single contract and let it read only that contract's debt details and boletos. You choose the allowed operations, so the agent runs only the reads and negotiations you authorize and nothing else.

Tsp7 API TSP

Name: API TSP API
Brand: API TSP
Availability: InStock

Browse all Swaggerhub Tsp7 APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically boletosfinanciado, dadoscontrato. Covers 11 operations.

Use for: I need to boletosfinanciado, I want to dadoscontrato, Search for detalhesdivida, Find all detalhesdividaparelado

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

Esta é a documentação da API TSP. The API exposes 11 endpoints.

Jentic One on Github View OpenAPI Document