canonical: https://jentic.com/apis/strikedm.com/strikedm

# Strikedm StrikeAI API

AI-driven lead response management and conversational AI platform API. The API exposes 6 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create lead, list leads. Covers 6 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create lead
- List leads
- Get lead
- Update lead
- Monitor StrikeAI API operational status and events

## Use cases

### Communications Operations

Use the StrikeAI API to perform communications operations programmatically. The API provides 6 endpoints covering core functionality including create lead, list leads, get lead.

Example prompt: Call POST /leads to create lead

### Automated Leads Management

Automate leads operations by combining multiple StrikeAI API endpoints. Agents can list leads and then get lead in a single workflow.

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

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/leads` | Create lead |
| GET | `/leads` | List leads |
| GET | `/leads/{id}` | Get lead |
| PUT | `/leads/{id}` | Update lead |
| POST | `/conversations` | Create conversation |
| GET | `/conversations` | List conversations |

## Key resources

- **Leads** — Lead management
- **Conversations** — Conversation tracking

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/strikedm.com/strikedm/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 StrikeAI API by hand means sending your key in the X-API-Key header on every request and tracking lead and conversation ids yourself. Through Jentic you install once, import the StrikeAI API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** StrikeAI puts the lead id in the URL path (`/leads/{id}`), so a rule can pin your agent to one lead: it can read and update that lead and nothing else. You choose the operations it may call, so you can grant reading a lead without granting the ability to update it.
- **Credential handling:** Your StrikeAI API key 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 'create a lead' or 'start a conversation', and Jentic returns the matching StrikeAI 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 StrikeAI API use?

The StrikeAI API uses an API key passed in the `X-API-Key` 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 create lead with the StrikeAI API?

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

### What are the rate limits for the StrikeAI 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 create lead through Jentic?

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

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

The StrikeAI API exposes 6 endpoints covering leads, conversations operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which StrikeAI operations and credentials the agent may use. Because StrikeAI puts the lead id in the URL path (`/leads/{id}`), you can pin the agent to a single lead so it can read and update that lead and nothing else. You also choose which operations it may call, granting GET `/leads/{id}` to read a lead while withholding PUT `/leads/{id}` or POST /leads so it cannot update or create.