Install Jentic One Beta

Connect the Drop Cowboy Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Drop Cowboy Public 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%2Fdropcowboy.com%2Fdropcowboy" | 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%2Fdropcowboy.com%2Fdropcowboy" | 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 Drop Cowboy Public API.

Send ringless voicemail, SMS and RCS texts, email, voice broadcasts, and AI calls

Manage contacts with tags, notes, follow-ups, lists, dispositions, and owners

Create and run campaigns, start and pause them, and read their statistics

Rent and configure phone numbers, lines, and IVRs

Build, publish, and manage AI agents that place and handle calls

GET STARTED

Start building with Drop Cowboy Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Drop Cowboy Public API for, with concrete tasks.

★ Agent-driven outbound outreach

An AI agent connected through Jentic can run a compliant outreach sequence: create a contact, check it against the do-not-contact list, and send a ringless voicemail or text. Because sends return a 202 and report their outcome to a callback URL, the agent can log that a message was queued and later reconcile delivery against the status webhook rather than blocking on the send.

Create a contact, confirm it is not on the do-not-contact list, then send a ringless voicemail and record the returned request id.

Campaign orchestration

Drop Cowboy models outreach as campaigns that can be created, started, paused, and measured. An agent can launch a voice broadcast campaign against a contact list, pause it if a budget threshold is hit, and pull campaign statistics to report delivery and response rates back to the operator.

Create a campaign, start it against a contact list, then read its statistics and pause it if delivery falls below a threshold.

Phone number provisioning

The phone endpoints search for available numbers, rent them, import numbers a customer already owns, and configure the lines behind them. An agent setting up a new sending identity can search for a number in a given area, rent it, and attach it to a line without a support ticket.

Search for an available phone number in a target area code, rent it, and confirm it is listed on the account.

Consent and compliance tracking

Drop Cowboy records per-contact consent and maintains a do-not-contact list, so outreach stays within the rules. An agent can record consent when a contact opts in, revoke it on request, and check any number against the do-not-contact list before a send, keeping a defensible audit trail.

Record consent for a contact who opted in, then check their number against the do-not-contact list before sending.

Key Endpoints

175 endpoints — the drop cowboy api sends outbound messages across channels: ringless voicemail, sms and rcs texts, email, voice broadcasts, and ai calls.

METHOD

PATH

DESCRIPTION

POST

/rvm

Send a ringless voicemail

POST

/sms

Send a text

POST

/voice-broadcast

Send a voice broadcast

POST

/ai-broadcast

Send an AI call

POST

/contact/public/contacts

Create contacts

GET

/campaign/public/campaigns

List campaigns

POST

/campaign/public/campaigns/{id}/start

Start a campaign

POST

/phone/public/numbers/rent

Rent phone numbers

POST

/rvm

Send a ringless voicemail

POST

/sms

Send a text

POST

/voice-broadcast

Send a voice broadcast

POST

/ai-broadcast

Send an AI call

POST

/contact/public/contacts

Create contacts

GET

/campaign/public/campaigns

List campaigns

POST

/campaign/public/campaigns/{id}/start

Start a campaign

POST

/phone/public/numbers/rent

Rent phone numbers

Why Jentic?

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

Setup

Wiring Drop Cowboy by hand means sending the x-key and x-secret headers or managing an oauth2 client-credentials token with the right scopes, and handling asynchronous 202 sends whose outcome arrives later on a callback URL and webhooks. Through Jentic you install once, import Drop Cowboy from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Drop Cowboy's oauth2 tokens carry per-operation scopes such as contacts:read and campaigns:write, so a rule can grant your agent only the scopes it needs. You choose the operations it may call, so send scopes like ringless voicemail or text are not included unless you add them.

Credential isolation

Your Drop Cowboy API key and secret, and any oauth2 token, are stored 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 'send a ringless voicemail' or 'start a campaign', and Jentic returns the matching Drop Cowboy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Drop Cowboy Public API through Jentic.

What authentication does the Drop Cowboy API use?

Per its OpenAPI spec, Drop Cowboy accepts an API key and secret sent as the x-key and x-secret headers, or an oauth2 client-credentials bearer token whose scopes each operation lists, with additional bearer JWT schemes for portal and embed contexts. A request satisfies auth by presenting the key-and-secret pair or a scoped token. Through Jentic these credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context.

Is there a Drop Cowboy MCP server?

You don't need an MCP server to give your agent the Drop Cowboy API. Jentic connects it directly from the API Directory: import Drop Cowboy, store your key and secret once, and your agent calls its operations. Operations are discovered on demand, so no extra server's tool definitions are loaded into the agent's context.

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

Yes. Drop Cowboy's oauth2 tokens carry per-operation scopes, so you can write a rule that grants only the ones your agent needs, such as contacts:read for lookups, while withholding send scopes. Combined with Jentic rules you can allow the read and campaign-status operations but keep ringless voicemail and text sends out of reach unless you add them, and every call the agent makes is logged.

Can I send a ringless voicemail with the Drop Cowboy API?

Yes. The ringless voicemail send endpoint accepts the recipient and media and returns a 202, meaning the request was accepted; the actual result arrives on your callback URL and status webhooks, so a 202 does not by itself mean the send succeeded. The same asynchronous pattern applies to the SMS, voice broadcast, and AI call sends.

What are the rate limits for the Drop Cowboy API?

The OpenAPI spec does not publish numeric rate limits; it instructs clients to branch on the HTTP status and retry 429 and 5xx responses with exponential backoff and jitter. Check the Drop Cowboy developer documentation for the current limits before running high-volume campaigns.

How do I send a text with the Drop Cowboy API through Jentic?

Install Jentic One, import Drop Cowboy from the API Directory, and store your API key and secret once. Your agent then searches by intent, for example 'send a text', and Jentic returns the matching send operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Drop Cowboy Public API

AI ReadinessNon-Ready (D)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice TelephonyapiKey, oauth2, bearer175 EndpointsREST

For Agents

Send ringless voicemail, SMS and RCS, email, voice broadcasts, and AI calls, and manage the contacts, campaigns, phone numbers, and AI agents behind them. Sends are asynchronous with results delivered to callback URLs and status webhooks.

Use for: Send a ringless voicemail to a contact, Send a text message to a phone number, Create a contact and add it to a list, Start a voice broadcast campaign

Not supported: Does not handle payment billing, support ticketing, or CRM deal pipelines. Use for outbound multi-channel messaging campaigns and the contacts behind them only.

The Drop Cowboy API sends outbound messages across channels: ringless voicemail, SMS and RCS texts, email, voice broadcasts, and AI calls. It manages the contacts, tags, lists, and campaigns behind those sends, rents and configures phone numbers and IVR lines, and builds AI agents that place and handle calls. Sends are asynchronous and return a 202, with results delivered to a callback URL and status webhooks, and the API records consent and maintains a do-not-contact list for compliant outreach.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: FSignals: 4

19%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

88%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C-Signals: 4

Example Density

How richly the API is illustrated with examples.

43%

Example Validity

Percentage of examples that conform to their schemas.

52%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

40%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: CSignals: 1

55%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: BSignals: 1

66%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Drop Cowboy Public API to your agent

Capabilities

Start building with Drop Cowboy Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Drop Cowboy Public API

Jentic AI Readiness Score

Drop Cowboy Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness