---
title: "Answering Service Care for developers and agents"
description: "Public API, OpenAPI document, customer API, MCP server, and machine-readable files for integrating with Answering Service Care."
canonical: "https://answeringservicecare.com/developers/"
---

# Answering Service Care for developers and agents

Answering Service Care (ASC) is a 24/7 US-based answering service with live and AI receptionists. This page lists every way software and AI agents can work with ASC: a public read-only API, the authenticated customer API, an MCP server, and machine-readable versions of the site.

### Public API

Base URL: `https://answeringservicecare.com/api/v1`. No API key or account is needed; every operation is read-only and returns JSON. The full contract, with operation IDs and response schemas, is in the [OpenAPI 3.1 document](https://answeringservicecare.com/openapi.json).

| Endpoint | Operation | Returns |
|---|---|---|
| `GET /company` | `getCompany` | Company profile: name, description, phone, email, mailing address, service area, social profiles, and links to key pages. |
| `GET /services` | `listServices` | Every service ASC offers, with a description, page URL, and markdown URL. |
| `GET /pricing` | `getPricing` | Every plan for each service, billed monthly or annually: price, minutes or chats included, rate for extra minutes or chats, features. |
| `GET /search?q={words}` | `searchSite` | Search service, industry, location, and blog pages. Each result has a title, summary, page URL, markdown URL, and last-updated date. |

#### Quickstart

 CODE0

#### Errors

Errors are JSON with an HTTP status, a machine-readable `code`, a `message`, a `hint` explaining how to fix the request, and a `documentation_url`. For example, an unknown path returns `404` with `"code": "rest_no_route"`.

#### Batch requests and async jobs

`POST https://answeringservicecare.com/api/v1/batch` runs up to 10 of the GET operations above in one request and returns each one's status and body. Each operation counts toward the rate limit. Add `Prefer: respond-async` to get `202 Accepted` with a `Location` header instead; fetch that job URL (valid for 24 hours) for the results. An `Idempotency-Key` header is echoed back so you can match responses to requests; because the API changes nothing, repeating a request is always safe.

 CODE1

#### Sandbox

`https://answeringservicecare.com/api/sandbox/v1` serves the same endpoints, including `/batch`, with fixed test data that never changes, so tests and demos don't depend on live prices. Sandbox responses include `"sandbox": true`. The OpenAPI document lists it as a second server.

### Customer API

Existing ASC customers can read their messages, call recordings, and to-dos, and connect Zapier or external dispatching, through the customer REST API. Credentials are issued to customers. See the [API reference](https://answeringservicecare.com/docs/api-reference/).

### MCP servers

The public Model Context Protocol server at `https://answeringservicecare.com/mcp` needs no account or key. Connect any MCP client over Streamable HTTP to get the public API's data as read-only tools: `get_company_info`, `list_services`, `get_pricing`, `search_site`, and `read_page`. The [server card](https://answeringservicecare.com/.well-known/mcp/server-card.json) lists each tool's inputs, and the server is listed in the [official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=com.answeringservicecare/public) as `com.answeringservicecare/public`.

Existing customers can also connect to their account through the server at `https://mcp.answeringservicecare.com/api/v2/mcp`. It is protected with OAuth 2.0; its tools are listed after authorization. The [authentication guide](https://answeringservicecare.com/auth.md) walks through discovery and sign-in, and the [account server card](https://answeringservicecare.com/.well-known/mcp/account-server-card.json) describes it.

The documentation, including the customer API reference, has its own read-only MCP server at `https://answeringservicecare.com/docs/~gitbook/mcp`, with the tools `searchDocumentation`, `getPage`, and `askQuestion`. It needs no key; its [server card](https://answeringservicecare.com/.well-known/mcp/docs-server-card.json) lists the inputs.

### Agent skills and plugin

The [Answering-Service-Care/agent-skills](https://github.com/Answering-Service-Care/agent-skills) repository on GitHub packages ASC's two agent skills (researching ASC, and estimating plan cost for a call volume) as an Agent Plugin, together with the MCP server configuration. Install the skills in Claude Code, Codex, Cursor, and other agents with:

 CODE2

### SDKs and CLI

Official clients for the public API, with no dependencies, are published as `answeringservicecare` on [npm](https://www.npmjs.com/package/answeringservicecare) (JavaScript and TypeScript) and [PyPI](https://pypi.org/project/answeringservicecare/) (Python). Both include an `answeringservicecare` command that prints JSON. Source: [Answering-Service-Care/sdk](https://github.com/Answering-Service-Care/sdk).

 CODE3

### Limits, pagination, and versioning

The public API allows 60 requests per minute per client. Every response carries `RateLimit-Policy` and `RateLimit` headers (plus `X-RateLimit-*`); over the limit you get a JSON `429` with `Retry-After`. Search is cursor-paginated: pass a response's `nextCursor` back as `cursor`.

The major version is in the path (`/api/v1`). Changes within v1 only add endpoints, fields, and optional parameters. A breaking change ships as `/api/v2`, and v1 keeps working for at least 12 months after that, with `Deprecation` and `Sunset` headers on its responses and a notice on this page.

### Machine-readable files

| URL | What it is |
|---|---|
| [`/llms.txt`](https://answeringservicecare.com/llms.txt) | Curated index of the site for language models. |
| [`/llms.md`](https://answeringservicecare.com/llms.md) | When to use ASC, how to call it, and where everything is. |
| [`/AGENTS.md`](https://answeringservicecare.com/AGENTS.md) | Usage notes for AI agents. |
| [`/pricing.md`](https://answeringservicecare.com/pricing.md) | Every plan and price as markdown. |
| [`/index.md`](https://answeringservicecare.com/index.md) | The homepage as markdown. Any page works: drop the trailing slash and add .md. |
| [`/?mode=agent`](https://answeringservicecare.com/?mode=agent) | JSON summary of capabilities, endpoints, and authentication. |
| [`/ask?query=bilingual+answering+service`](https://answeringservicecare.com/ask?query=bilingual+answering+service) | NLWeb-style natural-language search. Returns JSON, or server-sent events with ?streaming=true. |
| [`/.well-known/api-catalog`](https://answeringservicecare.com/.well-known/api-catalog) | RFC 9727 API catalog. |
| [`/.well-known/ai-catalog.json`](https://answeringservicecare.com/.well-known/ai-catalog.json) | Agentic resource catalog (also at /.well-known/ard.json). |
| [`/.well-known/agent-skills/index.json`](https://answeringservicecare.com/.well-known/agent-skills/index.json) | Agent skills index with SKILL.md files. |
| [`/.well-known/mcp/server-card.json`](https://answeringservicecare.com/.well-known/mcp/server-card.json) | Public MCP server card, with its tool list. |
| [`/.well-known/mcp/account-server-card.json`](https://answeringservicecare.com/.well-known/mcp/account-server-card.json) | Account MCP server card. |
| [`/.well-known/mcp/docs-server-card.json`](https://answeringservicecare.com/.well-known/mcp/docs-server-card.json) | Docs MCP server card. |
| [`/schemamap.xml`](https://answeringservicecare.com/schemamap.xml) | NLWeb Schema Map listing the schema.org feed (/feeds/schema.jsonl). |

### Starting service

There is no sign-up API: a person chooses a plan on the [pricing page](https://answeringservicecare.com/pricing/) or talks to sales on the [contact page](https://answeringservicecare.com/contact-us/). For questions about integrations, contact ASC there as well.
