Zocks API

Name: Zocks API
Brand: Zocks API
Availability: InStock

✓ Official Vendor SpecCommunicationsSms Messagingbearer14 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Zocks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zocks 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%2Fzocks.io%2Fzocks" | 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%2Fzocks.io%2Fzocks" | 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 Zocks API.

Send message

List messages

Get message

Delete message

GET STARTED

Start building with Zocks API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Zocks API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

14 endpoints — privacy-focused communications platform api for managing conversations, messages, and user interactions.

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

POST

/messages

Send message

GET

/messages

List messages

GET

/messages/{messageId}

Get message

DELETE

/messages/{messageId}

Delete message

POST

/conversations

Create conversation

GET

/conversations

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Zocks API through Jentic.

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.

Zocks API

Connect the Zocks API to your agent

Capabilities

Start building with Zocks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs