canonical: https://jentic.com/apis/zocks.io/zocks

# Zocks API

Privacy-focused communications platform API for managing conversations, messages, and user interactions. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

Programmatically send message, list messages. Covers 14 operations with bearer authentication.

## Scope

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

## Capabilities

- Send message
- List messages
- Get message
- Delete message
- Create conversation

## Use cases

### Communications Operations

Use the Zocks API to perform communications operations programmatically. The API provides 14 endpoints covering core functionality including send message, list messages, get message.

Example prompt: Call POST /messages to send message

### Automated Messages Management

Automate messages operations by combining multiple Zocks API endpoints. Agents can list messages and then get message in a single workflow.

Example prompt: Call GET /messages to list messages, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'send message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages` | Send message |
| GET | `/messages` | List messages |
| GET | `/messages/{messageId}` | Get message |
| DELETE | `/messages/{messageId}` | Delete message |
| POST | `/conversations` | Create conversation |
| GET | `/conversations` | List conversations |
| GET | `/conversations/{conversationId}` | Get conversation |
| PUT | `/conversations/{conversationId}` | Update conversation |

## Key resources

- **Messages** — Message operations
- **Conversations** — Conversation management
- **Users** — User management
- **Channels** — Channel operations

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zocks.io/zocks/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 Zocks by hand means setting its bearer token on every request against the api.zocks.io host and shaping message and conversation payloads yourself. Through Jentic you install once, import Zocks from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Zocks puts the conversation id in the URL path (`/conversations/{conversationId}`), so a rule can pin your agent to one conversation: it can read and update that conversation and nothing else. You choose the operations it may call, so destructive ones like message deletion are not included unless you add them.
- **Credential handling:** Your Zocks 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 'send a message' or 'start a conversation', and Jentic returns the matching Zocks operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Zocks API use?

The Zocks API uses a Bearer token in the Authorization header. 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 send message with the Zocks API?

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

### What are the rate limits for the Zocks 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 send message through Jentic?

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

### How many endpoints does the Zocks API have?

The Zocks API exposes 14 endpoints covering messages, conversations, users operations.

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

Yes. Because you run Jentic One yourself, you decide which Zocks operations your agent may call and which credentials it may use. Since the conversation id lives in the URL path (`/conversations/{conversationId}`), you can pin the agent to a single conversation so it only reads and updates that one and nothing else. Destructive operations such as message deletion via DELETE `/messages/{messageId}` are excluded unless you explicitly add them.