canonical: https://jentic.com/apis/pitchyes.com.br/pitchyes

# PitchYes API

The PitchYes API places outbound AI phone calls and manages the contacts and agents behind them. It triggers calls directly or from a CRM assistant, attaches custom metadata to each call, and records a searchable call history retrievable by id. Contact operations create, update, delete, and bulk-import contacts, while agent operations create, edit, list, and remove the AI agents that run the calls. It is a focused interface for voice outreach and the records it produces.

## For AI agents

Place outbound AI phone calls, attach metadata, and review call history on PitchYes. Agents can also create and manage contacts and the AI calling agents that run the calls.

## Scope

Does not handle SMS, email, or live chat. Use for outbound AI voice calls and their contacts only.

## Capabilities

- Trigger outbound AI phone calls directly or from a CRM assistant
- Send calls with custom metadata attached
- Search call history and retrieve a call by its id
- Create, update, delete, and bulk-import contacts
- Create, edit, list, and remove AI calling agents

## Use cases

### AI Agent Outbound Calling

An AI agent connected through Jentic can place a voice call to a contact and attach the context it should carry, without a human dialing. The agent searches for the send-call operation, PitchYes returns its input schema, and the agent submits the contact and metadata. This supports follow-up, reminder, and qualification call flows.

Example prompt: Place an outbound call to a contact and attach a campaign reference as metadata

### Contact Management

Create and update the contacts PitchYes calls, delete ones that are no longer needed, and bulk-import a list to seed a campaign. This keeps the calling list current without manual data entry in a dashboard.

Example prompt: Create a contact and import a list of additional contacts

### Call History Review

Search the record of placed calls and retrieve any single call by its id to inspect its outcome and metadata. An agent can reconcile what was called and when for reporting or follow-up decisions.

Example prompt: Search recent call history and retrieve one call by its id

### Calling Agent Configuration

Create the AI agents that run PitchYes calls, edit their configuration, list the ones that exist, and remove agents that are retired. This lets an operations tool manage the roster of calling agents programmatically.

Example prompt: Create a calling agent and list all configured agents

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/calls/send` | Send a call with metadata |
| POST | `/calls/crm/{assistantId}` | Trigger a call from a CRM assistant |
| GET | `/calls/historico` | Call history |
| GET | `/calls/get/{id}` | Get a call by id |
| POST | `/contatos/criar` | Create a contact |
| POST | `/contatos/lista` | Import a contact list |
| POST | `/agent/create` | Create a calling agent |
| GET | `/agent/getall` | List all agents |

## Key resources

- **Calls** — Trigger calls, attach metadata, and read call history
- **Contacts** — Create, update, delete, and bulk-import contacts
- **Agents** — Create, edit, list, and remove AI calling agents

## AI readiness

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.

- **Score:** 37 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 15 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 56 / 100
- **View full report:** https://jentic.com/apis/pitchyes.com.br/pitchyes/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the PitchYes API by hand means setting up JWT Bearer auth and mapping its call, contact, and agent operations yourself. Through Jentic you install once, import PitchYes from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** PitchYes separates its read operations (call history and lookups) from write operations that place calls, change contacts, and manage agents, so a rule can hold your agent to the ones it needs. You choose the operations it may call, so placing a call or deleting a contact is not included unless you add it.
- **Credential handling:** Your PitchYes token 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 'place an outbound call' or 'create a contact', and Jentic returns the matching PitchYes operation with its input schema so the agent calls the right endpoint without reading the docs.

## Related APIs

- **Bland AI** — Programmable AI phone calls with configurable agents.
- **Retell AI** — Build and run AI voice agents for phone conversations.
- **Twilio Voice** — Low-level programmable voice calling infrastructure.
- **Plivo** — Voice and SMS communications platform.

## FAQ

### What authentication does the PitchYes API use?

The PitchYes API authenticates with a JWT Bearer token per its OpenAPI spec: send it in the Authorization header. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

### Can I place outbound calls with the PitchYes API?

Yes. Send a call with custom metadata, or trigger one from a CRM assistant by its id, then search the call history and retrieve any call by its id to check the outcome.

### Is there a PitchYes MCP server?

You don't need an MCP server to give your agent the PitchYes API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the call, contact, and agent endpoints it needs.

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

Yes. Write a rule that allows only the call-history and lookup reads, so a reporting agent can review calls while placing new calls, editing contacts, and deleting agents stay out of reach, and every call it makes is logged.

### What are the rate limits for the PitchYes API?

The OpenAPI spec does not specify rate limits. Check pitchyes.com.br or your account dashboard for the limits that apply to your plan.

### How do I place a call with the PitchYes API through Jentic?

Search Jentic for an intent like 'place an outbound call', and it returns the PitchYes send-call operation with its input schema so your agent calls it with a contact and metadata. Your stored token is injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.