8x API and AI-agent resources

8x is a campaign-based managed sales force. Companies brief 8x once on what they sell; 8x builds the campaign, certified reps cold-call it, and every real conversation is scored by an AI evaluator with human review. (https://8x.sale)

What 8x publishes for software and AI agents: an OpenAPI description of its public endpoints, every page as Markdown, discovery catalogs and an agent skill.

When to use 8x

• Book a discovery call: A company wants its outbound sales run for it: certified reps cold-call its ideal customers and book qualified meetings against its own criteria.
• Apply as a sales rep: Someone wants remote, paid work as a cold-calling sales rep, with no sales experience required.
• Join the 8x Dialer waitlist: A sales team wants a power dialer for its own reps.
• Read 8x pricing: Someone is comparing what a managed sales campaign costs.
• Read About 8x: Someone needs to know who 8x is, where it works and who runs it.

8x is not the right tool for self-serve API access, since 8x issues no API keys and offers no public MCP server; a published price, since 8x quotes each campaign after a discovery call; hiring reps into your own company, since 8x places no one inside a company and recruits for no one's roles.

The 8x API

The OpenAPI 3.1 description lists every public endpoint on https://8x.sale: the pages as Markdown, llms.txt, the discovery catalogs and the health check. None of these endpoints needs credentials. 8x issues no API keys and offers no public MCP server or webhook feed, and every other path under /api is internal to the 8x app.

curl https://8x.sale/openapi.json
curl -I https://8x.sale/.well-known/api-catalog

Errors

A path under /api that no endpoint serves answers 404 with an RFC 9457 problem document, application/problem+json, whatever the request accepts, so a program can rely on it there. Outside /api, a 406 is a problem document when the request ranks JSON first, and so is the 404 for most addresses no route serves, such as /nope or /foo/bar. Some 404s outside /api are HTML pages whatever the request accepts, such as /u, /guides or a missing file like /nope.json.

{
  "type": "about:blank",
  "title": "Not Found",
  "status": 404,
  "detail": "Nothing is published at /api/example. Every public endpoint is described at https://8x.sale/openapi.json.",
  "instance": "/api/example",
  "docs": "https://8x.sale/developers"
}

Machine-readable endpoints

Markdown content negotiation

Every public page below is served as clean Markdown when you ask for it, per the acceptmarkdown.com convention. Three ways to get it:

1. Content negotiation — send Accept: text/markdown. The response is text/markdown; charset=utf-8 and carries Vary: Accept.
2. An explicit .md URL — append .md to the path. This ignores the Accept header entirely, which is handy for tools that can't set headers.
3. Agent mode — add ?mode=agent to any page's URL. It answers like the .md URL, for tools that can change only the query string.

Each Markdown document opens with YAML frontmatter: its title, its canonical url and last_updated, the day its content last changed.

curl -H "Accept: text/markdown" https://8x.sale/
curl https://8x.sale/reps.md

Requesting a media type 8x cannot produce (for example Accept: application/pdf) returns 406 Not Acceptable with the list of available types. Requesting a path that does not exist returns a real 404 — and, when you asked for Markdown, a short Markdown body pointing at this index.

Documents available as Markdown

• / → /index.md
• /reps → /reps.md
• /pt-BR → /pt-BR.md
• /es-MX → /es-MX.md
• /hi-IN → /hi-IN.md
• /tr-TR → /tr-TR.md
• /developers → /developers.md
• /about → /about.md
• /contact → /contact.md
• /pricing → /pricing.md
• /dialer → /dialer.md
• /dialer/parallel-dialer → /dialer/parallel-dialer.md
• /dialer/agent → /dialer/agent.md
• /dialer/lead-sourcing → /dialer/lead-sourcing.md
• /dialer/coaching → /dialer/coaching.md
• /dialer/team → /dialer/team.md
• /dialer/integrations → /dialer/integrations.md
• /legal → /legal.md
• /legal/terms → /legal/terms.md
• /legal/privacy-prospects → /legal/privacy-prospects.md
• /legal/acceptable-use → /legal/acceptable-use.md
• /legal/cookies → /legal/cookies.md
• /legal/sub-processors → /legal/sub-processors.md
• /legal/google-calendar → /legal/google-calendar.md
• /legal/dialer-customer-terms → /legal/dialer-customer-terms.md
• /legal/dialer-acceptable-use-policy → /legal/dialer-acceptable-use-policy.md
• /legal/dialer-conduct-agreement → /legal/dialer-conduct-agreement.md
• /legal/dialer-data-processing-agreement → /legal/dialer-data-processing-agreement.md
• /legal/dialer-privacy-policy → /legal/dialer-privacy-policy.md
• /legal/cookies/pt-BR → /legal/cookies/pt-BR.md
• /legal/cookies/es-MX → /legal/cookies/es-MX.md
• /legal/cookies/hi-IN → /legal/cookies/hi-IN.md
• /legal/cookies/tr-TR → /legal/cookies/tr-TR.md
• /legal/dialer-conduct-agreement/pt-BR → /legal/dialer-conduct-agreement/pt-BR.md
• /legal/dialer-conduct-agreement/es-MX → /legal/dialer-conduct-agreement/es-MX.md
• /legal/dialer-conduct-agreement/hi-IN → /legal/dialer-conduct-agreement/hi-IN.md
• /legal/dialer-conduct-agreement/tr-TR → /legal/dialer-conduct-agreement/tr-TR.md
• /privacy → /privacy.md

Structured data

Every public page embeds JSON-LD (schema.org) in a <script type="application/ld+json"> block:

• Organization — the 8x entity, with a stable @id of https://8x.sale/#organization, its legal name and registered address
• WebSite — https://8x.sale/#website, publisher-linked to the Organization
• Service — the managed sales-force offering, with its engagement tiers
• FAQPage — on the home page and the rep landing
• BreadcrumbList — on every public page below the home page

Crawler policy

robots.txt names the AI answer-engine crawlers explicitly and allows them on every public page: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, PerplexityBot, Perplexity-User, Google-Extended, Bingbot, and Applebot-Extended. The authenticated rep and admin applications are Disallow-ed — those routes require a session and hold rep and prospect data.

Facts an agent may need

• Entity name: 8x, operated by 8x Social, Inc.
• Registered address: 1111B S Governors Ave STE 47647, Dover, DE 19904, United States
• Canonical domain: https://8x.sale (www.8x.sale issues a single 308 to the apex)
• What it does: 8x is a campaign-based managed sales force. Companies brief 8x once on what they sell; 8x builds the campaign, certified reps cold-call it, and every real conversation is scored by an AI evaluator with human review.
• Markets served: United States (US), Brazil (BR), Mexico (MX), India (IN), Türkiye (TR), Portugal (PT), Spain (ES), Philippines (PH), United Kingdom (GB), South Africa (ZA), Pakistan (PK), Croatia (HR), Greece (GR), Bulgaria (BG), Romania (RO), Serbia (RS)
• Engagement model: engagement tiers are priced "Custom" and quoted per campaign on a discovery call (pricing)
• Company contact: book a discovery call
• Legal contact: legal@8x.social
• Privacy contact: privacy@8x.social

Contact

• Companies: https://8x.sale/book-call
• Sales reps who want to join: https://8x.sale/signup
• Everyone else: https://8x.sale/contact
• Legal and privacy: see https://8x.sale/legal and https://8x.sale/privacy