canonical: https://jentic.com/apis/swaggerhub.semcompany-ae4/api-de-contatos

# Semcompany Ae4 API de Contatos

Aplicação para gerenciamento de contatos de pessoas e organizações. The API exposes 3 endpoints.

## For AI agents

Programmatically cadastrar uma pessoa, listar pessoas cadastradas. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Cadastrar uma pessoa
- Listar pessoas cadastradas
- Obter uma pessoa especifica por meio do ID
- Query and filter API de Contatos records by parameters
- Monitor API de Contatos operational status and events

## Use cases

### Identity and Authentication Operations

Use the API de Contatos to perform identity auth operations programmatically. The API provides 3 endpoints covering core functionality including cadastrar uma pessoa, listar pessoas cadastradas, obter uma pessoa especifica por meio do id.

Example prompt: Call POST /pessoas to cadastrar uma pessoa

### Automated Pessoas Management

Automate pessoas operations by combining multiple API de Contatos endpoints. Agents can listar pessoas cadastradas and then obter uma pessoa especifica por meio do id in a single workflow.

Example prompt: Call GET /pessoas to listar pessoas cadastradas, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API de Contatos 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.

Example prompt: Search Jentic for 'cadastrar uma pessoa', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /pessoas | Cadastrar uma pessoa |
| GET | /pessoas | Listar pessoas cadastradas |
| GET | /pessoas/{idPessoa} | Obter uma pessoa especifica por meio do ID |

## Key resources

- **Pessoas** — Operations related to Pessoas

## Why Jentic

- **Setup:** Wiring API de Contatos by hand means standing up its base host and handling requests and retries yourself, even though it ships no auth scheme. Through Jentic you install once, import API de Contatos from the API Directory, store any connection details once, and your agent calls it.
- **Permission scoping:** API de Contatos puts the person id in the URL path (/pessoas/{idPessoa}), so a rule can pin your agent to one person: it can read that person and nothing else. You choose the operations it may call, so writes like creating a person are not included unless you add them.
- **Credential handling:** Any API de Contatos connection detail 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.
- **Discovery method:** Agents search Jentic by intent such as 'register a person' or 'look up a person by id', and Jentic returns the matching API de Contatos operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the API de Contatos use?

The API de Contatos 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 cadastrar uma pessoa with the API de Contatos?

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

### What are the rate limits for the API de Contatos?

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 cadastrar uma pessoa through Jentic?

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

### How many endpoints does the API de Contatos have?

The API de Contatos exposes 3 endpoints covering pessoas operations.

### Can I limit what my agent is allowed to do with the API de Contatos?

Yes. Because you run Jentic One yourself, your own rules decide which API de Contatos operations the agent may call and which connection details it may use. Since the person id sits in the URL path (/pessoas/{idPessoa}), you can pin the agent to a single person so it reads only that record via GET /pessoas/{idPessoa} and lists nothing else. You choose the operations it can reach, so writes such as POST /pessoas to register a person stay off unless you add them.