canonical: https://jentic.com/apis/quotecam.ai/quotecam

# QuoteCam API

QuoteCam API for managing video calls, clients, quotes, and webhooks. The API exposes 11 endpoints secured with bearer authentication.

## For AI agents

Programmatically create call, list calls. Covers 11 operations with bearer authentication.

## Scope

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

## Capabilities

- Create call
- List calls
- Get call by code
- Access QuoteCam API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the QuoteCam API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including create call, list calls, get call by code.

Example prompt: Call POST `/api/calls/create` to create call

### Automated Authentication Management

Automate authentication operations by combining multiple QuoteCam API endpoints. Agents can list calls and then get call by code in a single workflow.

Example prompt: Call GET `/api/calls` to list calls, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call QuoteCam 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 'create call', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/calls/create` | Create call |
| GET | `/api/calls` | List calls |
| GET | `/api/calls/by-code/{code}` | Get call by code |
| POST | `/api/clients` | Create client |
| GET | `/api/clients` | List clients |
| GET | `/api/videos` | List videos |
| GET | `/api/quotes` | List quotes |
| POST | `/api/webhooks/subscribe` | Subscribe to webhook |

## Key resources

- **Authentication** — Operations related to Authentication
- **Calls** — Operations related to Calls
- **Clients** — Operations related to Clients
- **Quotes** — Operations related to Quotes
- **Videos** — Operations related to Videos

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/quotecam.ai/quotecam/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 QuoteCam API by hand means learning its bearer auth, targeting the quotecam.ai host, and handling retries across its call, client, video, and quote operations yourself. Through Jentic you install once, import QuoteCam from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** QuoteCam puts the call code in the URL path (`/api/calls/by-code/{code}`), so a rule can pin your agent to reading one call by its code, while its create operations take their target in the request body. You choose the operations it may call, so a write like creating a client is not included unless you add it.
- **Credential handling:** Your QuoteCam 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 'create a QuoteCam call' or 'list quotes', and Jentic returns the matching QuoteCam operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the QuoteCam API use?

The QuoteCam 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 create call with the QuoteCam API?

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

### What are the rate limits for the QuoteCam 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 call through Jentic?

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

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

The QuoteCam API exposes 11 endpoints covering authentication, calls, clients operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which QuoteCam operations and credentials the agent may use. Because the call code sits in the URL path at GET `/api/calls/by-code/{code}`, you can pin the agent to reading a single call by its code while leaving out writes like POST `/api/calls/create` or POST `/api/clients`, which take their target in the request body. Only the operations you allow are exposed, so creating a client stays off limits unless you add it.