Let Agents In

Agent readiness · together.ai

2026-08-12 10:35 UTC · formula v9.2 · 6.0s

You publish files for machines to read, but nothing that tells one how to become a customer.

None of the nine known agent entry paths answered, including /agent-signup.md and /.well-known/agent-access.json. Reading is solved on your site; joining is not.

8/ 13

A dashed column is a stage we could not measure, not a stage you failed.

A · Discovery
4/5
B · Agent entry
1/4
C · Registration
n/m
D · Provisioning
1/2
E · Integration
2/2

of the 13 points that apply to you and we could measure · 4 of 17 were not scored

You 8 · category median 8 · best openrouter.ai 14 · 15 deterministic HTTP checks, published formula

Pass it onEmail itLinkedIn

Fix this first

+4points, taking 8/13 to 12/13, past fireworks.ai, baseten.co

This is the whole list: everything we could measure and you do not pass. Another 4 points sit behind checks we could not evaluate on your domain, and each of those lines below says what would make it measurable.

  1. 1
    llms.txt publishedminutes · +1

    Your llms.txt is already there. 1 of the 12 links we sampled are gone, starting with https://docs.together.ai/reference/delete_files-id. Fix those and this passes: a map an agent follows into a 404 costs it the budget it came with.

  2. 2
    Agent entry pointan afternoon · +2

    Publish /agent-signup.md: the path from nothing to a working key, written as steps for a machine rather than a tour for a person. Ours is at /agent-signup.md if you want a worked example, and it says plainly that we have nothing to sign up for.

  3. 3
    Programmatic key provisioningan afternoon · +1

    Document how a key is created without opening a dashboard: management API, service account or CLI. If no such path exists, that gap is the finding, not the docs.

Then, when you have room

  • MCP surface a project · +1You already talk about MCP, and nothing answered at the addresses named above. If your server is at another path, declare it at /.well-known/mcp.json: that file is what an agent reads first, and it is what makes the path stop mattering.

Take it with you

5 of the checks an agent depends on, together.ai does not pass.

Send yourself the list above with the checks that cost the most, and a permanent link. Whoever owns the fix is usually not the person who ran the scan.

One email with the report, and one follow-up asking what you did with it. No newsletter, no sequence. Delete on request at hello@letagentsin.com.

None of this tells you whether an agent picked you

Everything above is a file an agent could read. Whether one actually chose you is a different measurement, and we have not run it on together.ai. What we have run it on is a rich text editor vendor: six agents, one brief, six isolated copies of a real codebase. All six picked the same competitor, and the vendor being studied was never named, not even on a rejection list, while the runs named and dismissed ten alternatives between them. In an earlier round, run before we isolated the copies, it was named twice and struck off both times in four words: Fully commercial, licence key required. That study is about them, not about you. It is here because it is the difference between a file and a decision.

Against model hosting and gateways

You are 4 of 7 in a category where a developer is trying to call a model you did not train without running the GPUs.

  1. 1
    openrouter.ai
    14/15
  2. 2
    fireworks.ai
    11/15
  3. 3
    baseten.co
    9/14
  4. 4
    together.aiyou
    8/13
  5. 5
    replicate.com
    8/14
  6. 6
    modal.com
    8/15
  7. 7
    groq.com
    7/14

Where competitors pass and together.ai does not

  • llms.txt publishedopenrouter.ai · fireworks.ai · groq.com · modal.com
  • MCP surfaceopenrouter.ai · replicate.com · baseten.co
  • Programmatic key provisioningopenrouter.ai · fireworks.ai
  • Paths robots.txt points at answermodal.com

Only domains we have actually scanned appear here, so the ranking is a floor: a competitor missing from the list has not been measured, not beaten.

By stage

A
DiscoveryCan an agent find and read you?
4/5
B
Agent entryIs there a door built for a machine?
1/4
C
RegistrationCan an agent get an account?
not measured
D
ProvisioningCan it get credentials without a human?
1/2
E
IntegrationCan it ship working code?
2/2

Every check

Each line is one HTTP observation with a published rule, so you can rerun any of them yourself. Most are the same tomorrow if you are: the two that are not are the bot gate and the pricing page, which answer inconsistently on their own, which is why those run more than once and say so when the tries disagreed. PASS and PART are counted. UNMEASURED means we could not evaluate it, N/A means it does not apply to a product like yours, and neither is in the score or its denominator. See the formula

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-idA curated map of your docs is the cheapest way to control what an agent reads first. Worth one point and not more: in eighteen isolated agent runs across four categories, not one cited llms.txt among its sources, and an independent ninety-day measurement published by Otterly in February 2026 found it served 84 requests against 62,100 AI-bot visits.
  • 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 shellA markdown file written for a machine turns a guessing game into a procedure it can follow.
  • 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/mcpAn MCP server turns your API from something an agent reads about into something it can call.

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"Documented key creation is the difference between a two-minute integration and a support ticket.
  • 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

What we discovered on the way

Docs
https://docs.together.ai/intro · linked from the site
Pricing
https://www.together.ai/pricing · linked from the site
Signup
not found
npm package
together-ai (registry guess)
GitHub
togethercomputer/together-py
Package licence
Apache-2.0
Crawl-delay
none
Content-Signal
none
Blocked on-demand agents
none