Let Agents In

Agent readiness · Model hosting and gateways

fireworks.ai

11 of 15 measurable points under formula 9.2, measured on 2026-08-12. 15 checks exist; each is one HTTP request with a published rule, so every sentence below can be rerun and argued with. 1 of them could not be measured from where we ask, and those are left out of the denominator rather than counted as failures.

A · Discovery

  • PASS
    Answers an agent user-agentAnswered 200 to LetAgentsIn/1.0 (+https://letagentsin.com/methodology)
  • PASS
    llms.txt publishedllms.txt and llms-full.txt present at https://docs.fireworks.ai/llms.txt and https://docs.fireworks.ai/llms-full.txt, and the 12 links we sampled across both files all answer
  • PASS
    Docs readable without JavaScript12,459 characters of text without JS, on https://docs.fireworks.ai/api-reference/create-api-key rather than on https://docs.fireworks.ai/api-reference/introduction
  • PASS
    On-demand agents not blockedNo on-demand agent is blocked
  • N/A
    Paths robots.txt points at answerrobots.txt names no concrete path, only patterns or nothing, so there is no claim to check
  • PASS
    No punishing crawl delayNo Crawl-delay applies to the agents we check

B · Agent entry

  • FAIL
    Agent entry pointNone of the 9 known agent entry paths returns a file rather than your page shell
  • FAIL
    OAuth dynamic client registrationNo OAuth metadata on any of the 8 hosts probed, including the usual auth and api subdomains
  • FAIL
    MCP surfaceMCP mentioned 6x in your own files, but nothing answered at mcp.fireworks.ai, mcp.fireworks.ai/mcp, mcp.fireworks.ai/v1/mcp, api.fireworks.ai/mcp, /mcp or /api/mcp

C · Registration

  • PASS
    No CAPTCHA in the signup HTMLNo CAPTCHA vendor in the server HTML. A widget mounted later by JavaScript would not show here.
  • PASS
    Signup reachable without a browserForm renders in server HTML at https://fireworks.ai/signup

D · Provisioning

  • PASS
    Programmatic key provisioning3 of 7 provisioning phrases across the 6 documents we read: "management api", "create an api key (or api token, access token, personal access token, service account, auth token, secret key), next to something programmatic", "service account"
  • PASS
    Free tier or no-card trial stated in textFree tier or no-card signals at https://fireworks.ai/pricing: "free credits"

E · Integration

  • UNMEASURED
    Typed SDK on the registryUnmeasurable: we could not identify the package a developer installs to use you, from your site, your docs or a registry searchName your package once in your docs, or link it from your repository, and we stop guessing. If your product is not something a developer installs, this check does not apply to you: unmeasured is out of the score and out of the denominator, so it costs you nothing.
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://docs.fireworks.ai/api-reference/introduction

Tell me when this changes

The failures here are the kind nobody notices. An edge rule that starts refusing agents changes nothing a person sees in a browser, so the first sign is usually an integration that quietly stopped working. We rescan weekly and write only when a verdict moves.

This page is the newest scan we hold for fireworks.ai and changes when we rescan. It is not a judgement of the product: we measure whether an unattended run can get through, not whether the thing is any good. The whole corpus is published as JSON and CSV.

Scan a domain yourself