Earshot

Everything your Discord says, within earshot.

Early access for queryable archives and APIs over the Discord Servers in your plan.

observable historylive syncvisible coverageREST + MCP
example request
$ curl "https://api.earshot.gg/v1/servers/120381920000000000/search?q=refund" \
    -H "Authorization: Bearer esk_demo_earshot"
{
  "data": [{
    "message_id": "120381920000000011",
    "channel_id": "120381920000000001",
    "content": "refunds: /billing refund, up to 14 days",
    "discord_created_at": "2024-03-11T02:14:09Z",
    "discord_edited_at": null
  }],
  "page": { "next_cursor": null },
  "coverage": { "channels_total": 12, "channels_covered": 10, "status": "partial" },
  "as_of": { "archive_incarnation_id": "1d807584-4fd1-4ac9-99df-92c44e168f6f", "archive_revision": "48192" }
}
live continuity current200 OKmock response
Query

Query by channel, message ID, or time

Earshot maintains a query-ready archive of what the authorized Bot Connection can observe, with keyset pagination and Coverage that states what may be missing.

?channel_id=120381920000000001
Messages from one authorized channel.
?created_after=2026-05-01T00:00:00Z
Messages created after a timestamp.
?cursor=eyJ2IjoxLCJ...
The next slice using the opaque cursor returned by Earshot.
/v1/servers/:id/search?q=deploy+failed
Full-text search, optionally scoped to one channel.
/v1/servers/:id/messages/:message_id
One message's current archived state.
/v1/servers/:id/coverage
Per-channel sync detail and known gaps.

Build on a server's history

Give your agent ears

Point Claude, Cursor, or any MCP client at one URL with your API credential. No package, nothing to run.

One entry in your MCP config:

"earshot": { "url": "https://api.earshot.gg/mcp", "headers": { "Authorization": "Bearer esk_..." } }

Read-only tools over the authorized archive:

search_messagesget_messageslist_channels

Search what Earshot archived

Full-text search over current archived message content, optionally scoped to one channel.

/v1/servers/:id/search?q=refund+policy

Fetch one message

Read one message's current archived state by its Discord message ID.

GET /v1/servers/:id/messages/:message_id

Preview the API

Mock requests and responses show the planned demo experience. They do not call a live demo service yet. Pick an example:

Channels

List the channels you can query

One request returns the archived channels visible to your credential.

  • Scoped by the same access grant as message reads
  • Channel IDs stay decimal strings
  • Responses include data, page, coverage, and as_of
channels request
$ curl "https://api.earshot.gg/v1/servers/120381920000000000/channels" \
    -H "Authorization: Bearer esk_demo_earshot"

Select a Server Archive

Select

Choose an eligible Public Server Archive within your plan's Server Allowance.

Sync

Live intake starts first; Historical Sync imports the history Discord still exposes.

Query

Query committed data immediately while Historical Sync continues, with visible Coverage.

Earshot-operated Connection

Discord authorizes the bot; Earshot controls the Connection-wide Sync Scope. The bot does not post to the Server.

Request early access

Coverage, not guesswork

Historical Coverage, Live Continuity, and known Gaps stay visible while the archive is queryable.

Content deleted before observation or hidden by permissions cannot be recovered.

Pricing

Candidate plans while Earshot completes platform and legal review. A request is one API call; an MCP tool call counts the same. A shared read-only demo is planned.

Starter

For small communities.

$20/mo
  • Access to 3 Server Archives
  • Observable history + Coverage
  • 100k requests/mo
  • 10 req/s per credential
  • Message lookup by ID
Recommended

Pro

For agencies and multi-server teams.

$100/mo
  • Access to 25 Server Archives
  • Observable history + Coverage
  • 1M requests/mo
  • 50 req/s per credential
  • Coverage endpoint

Enterprise

For orgs with compliance needs.

Custom
  • Access to more than 25 Server Archives
  • SSO / SAML
  • DPA and custom retention
  • SLA and invoicing
Plan limits and features
LimitsStarterProEnterprise
Servers32525+
Message historyObservableObservableObservable
API requests100k/mo1M/moCustom
Rate limit10 req/s per credential50 req/s per credentialCustom
Full-text searchIncludedIncludedIncluded
Hosted MCPIncludedIncludedIncluded
Message lookupIncludedIncludedIncluded
Channel listingIncludedIncludedIncluded

Past 100% of your request cap we keep serving to 120% — with an email at 80% and 100% — then return 429 until the month resets or you upgrade. No overage billing.

The archive already has the answers.

Choose a server and query its observable history, live updates, and Coverage. One API.