arcmira.com valid

Arcmira

Arcmira is an SF-based AI company and the search engine for the spoken web. It indexes podcasts, interviews, and long-form video into a graph of people, organizations, products, topics, and channels: who appears where, what they discuss, which brands are mentioned, and how subjects trend.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:17:25.990Z. Cached copy · Source on arcmira.com

# Arcmira

> Arcmira is an SF-based AI company and the search engine for the spoken web. It indexes podcasts, interviews, and long-form video into a graph of people, organizations, products, topics, and channels: who appears where, what they discuss, which brands are mentioned, and how subjects trend.

The same index powers the public site and the HTTP JSON API at https://api.arcmira.com/v1. Search reads entities, mentions, and appearances, and never writes. Monitors are standing trackers with email, Slack, and HMAC-signed webhook delivery: create one with POST /v1/monitors and follow entities in it with POST /v1/monitors/{id}/entities. Transcripts use GET /v1/transcripts/{video_id}; an explicit Premium read starts a Premium transcript, using credits from the account's plan, then its on-demand budget. Report a wrong result with POST /v1/feedback, for free; see https://arcmira.com/docs/feedback.md. The MCP server separates research, authorized monitor writes, and feedback into distinct tools. Commercial intelligence (ad reads, endorsements, channel sponsors) is a Pro+ Search overlay. Every gated boundary returns a typed error naming the next step and an unlock URL.

URL patterns: append .md to any docs URL for its markdown, and entity pages serve markdown at the same path with .md appended, or with Accept: text/markdown. So /org/ramp is the HTML page, /org/ramp.md is its markdown, and /org/ramp/llms.txt stays as an alias for that same markdown. Every other page answers Accept: text/markdown rather than a .md twin, and / under that header is this file. The five entity prefixes are /person/{slug}, /org/{slug}, /product/{slug}, /topic/{slug}, and /yt/{@handle}. Channels also accept YouTube channel ids that start with UC. Transcripts are at /watch?v={videoId}.

Machine-readable entry points: https://arcmira.com/developers.md is the whole API in one file, https://arcmira.com/auth.md is the runbook for getting a credential, https://arcmira.com/.well-known/mcp is the MCP server card, and https://arcmira.com/.well-known/api-catalog is the linkset naming every discovery document. The docs are also an MCP server at https://arcmira.com/docs/mcp (no credential required to search and read public docs); the data is served by mcp.arcmira.com.

## Start here by situation

Each line is one situation and the single surface that answers it. Follow your line and stop reading this file.

- [I have no credentials yet](https://arcmira.com/auth.md): the whole sign-up runbook in one fetch. POST /v1/signups with an email, read the six digit code from that inbox, then POST /v1/signups/verify with the code. The 201 carries the account key (arc_sk_...), the header to send it in, account access details, and a curl for GET /v1/me, which reports tier, scopes, and remaining usage. Or sign in through an MCP host, which creates the account on the way. The long form, with key hygiene and the scope matrix, is the Authentication page listed under Docs below.
- [I am answering a user q
…

Machine-readable: GET /v1/resolve?q=arcmira.com · GET /v1/domain/arcmira.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for arcmira.com:
1. POST https://agentwebmap.com/v1/sites/arcmira.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://arcmira.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/arcmira.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/arcmira.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.