canonical: https://jentic.com/apis/strive.asia/strive-asia

# Strive Asia Strive APIs

Strive is a platform that empowers businesses to achieve BIG Customer Service with a Small Team through the Power of AI and Humanized Chatbots. The API exposes 6 endpoints.

## For AI agents

Programmatically add a new contact, retrieve contact. Covers 6 operations.

## Scope

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

## Capabilities

- Add a new contact
- Retrieve contact
- Integrate Strive APIs into automated workflows
- Query and filter Strive APIs records by parameters
- Monitor Strive APIs operational status and events

## Use cases

### Communications Operations

Use the Strive APIs to perform communications operations programmatically. The API provides 6 endpoints covering core functionality including add a new contact, retrieve contact, add a new product.

Example prompt: Call POST /zapier_addContact to add a new contact

### Automated Contacts Management

Automate contacts operations by combining multiple Strive APIs endpoints. Agents can retrieve contact and then add a new product in a single workflow.

Example prompt: Call POST /zapier_getContact to retrieve contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Strive APIs 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 'add a new contact', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/zapier_addContact` | Add a new contact |
| POST | `/zapier_getContact` | Retrieve contact |
| POST | `/zapier_addProduct` | Add a new product |
| POST | `/zapier_getProduct` | Retrieve product |
| POST | `/zapier_addDeal` | Add a new deal |
| POST | `/zapier_getDeal` | Retrieve deal |

## Key resources

- **Contacts** — Contact management operations
- **Products** — Product management operations
- **Deals** — Deal management 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 51 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/strive.asia/strive-asia/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:** The Strive APIs expose Zapier-style contact, product, and deal operations that you would otherwise wire and route yourself. Through Jentic you install once, import the Strive APIs from the API Directory, and your agent calls them without you hand-building the request plumbing.
- **Permission scoping:** Strive carries the contact, product, and deal targets in the request body rather than the URL path, so you limit the agent to the operations it needs, such as adding a contact or reading a deal. Because you choose the operations, adding a product or a deal is not available unless you include it in the allowed set.
- **Credential handling:** Any credential you configure for Strive 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 'add a new contact' or 'look up a deal', and Jentic returns the matching Strive 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 Strive APIs use?

The Strive APIs 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 add a new contact with the Strive APIs?

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

### What are the rate limits for the Strive APIs?

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 add a new contact through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'add a new contact'. Jentic returns the matching Strive APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Strive APIs have?

The Strive APIs exposes 6 endpoints covering contacts, products, deals operations.

### Can I limit what my agent is allowed to do with the Strive APIs?

Yes. Because you run Jentic One yourself, your own rules decide which Strive operations and credentials the agent may use. Strive carries the contact, product, and deal target in the request body rather than the URL path, so you can allow only the calls the agent needs, such as adding a contact with POST /zapier_addContact or reading a deal with POST /zapier_getDeal. Anything you leave out of the allowed set, like adding a product or creating a deal, stays unavailable to the agent.