Let Agents In

Agent readiness · Model hosting and gateways

together.ai

8 of 13 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. 3 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)
  • FAIL
    llms.txt publishedllms.txt and llms-full.txt present at https://www.together.ai/llms.txt and https://docs.together.ai/llms.txt and https://docs.together.ai/llms-full.txt, but 1 of the 12 links we sampled across both files are gone, starting with https://docs.together.ai/reference/delete_files-id
  • PASS
    Docs readable without JavaScript2,300 characters of text without JS
  • 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
  • PASS
    OAuth dynamic client registrationregistration_endpoint published, and client_credentials is among the 13 advertised grants, so an unattended agent has a documented path to a token
  • FAIL
    MCP surfaceMCP mentioned 1x in your own files, but nothing answered at mcp.together.ai, mcp.together.ai/mcp, mcp.together.ai/v1/mcp, api.together.ai/mcp, /mcp or /api/mcp

C · Registration

  • UNMEASURED
    No CAPTCHA in the signup HTMLUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.together.ai/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.
  • UNMEASURED
    Signup reachable without a browserUnmeasurable: we found no link to an account signup on the pages we read, while you publish prices at https://www.together.ai/pricing, so this is a gap in our reading rather than a finding about youLink signup from your home page or your pricing page and this becomes measurable.

D · Provisioning

  • PART
    Programmatic key provisioning1 of 7 provisioning phrases across the 4 documents we read: "management api"
  • UNMEASURED
    Free tier or no-card trial stated in textUnmeasurable: https://www.together.ai/pricing is larger than we read, so anything we did not find in it is a fact about our cap and not about your tiersNothing for you to do. A smaller pricing page, or one that states its tiers early, makes this measurable.

E · Integration

  • PASS
    Typed SDK on the registrytogether-ai@0.48.0 ships types, matched from the registry by who publishes it rather than by a link on your site
  • PASS
    Machine-readable API descriptionDocs serve markdown to machines, at https://docs.together.ai/intro

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 together.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