How to Search for Agent-Ready Services on Not Human Search

Updated

Not Human Search is a search engine for services that AI agents can actually use. You search by category, protocol, or the job your agent needs to complete, then compare results by their machine-readable readiness score. It's free to search, and organic rank is based on readiness, never payment. Use it when you need to find an API, tool, or service that an autonomous agent can discover and call without human intervention.

What you can search for

The search bar accepts three kinds of queries:

  • Category — e.g. ecommerce, finance, developer, data, security, health, productivity, ai-tools, hosting, other
  • Protocol — e.g. MCP, OpenAPI, llms.txt, ai-plugin, Schema.org
  • Task your agent needs to complete — e.g. AI jobs, payment API, weather, auth, hosting

The site suggests these examples directly under the search field, so you can start from a task description rather than guessing a category name.

Step-by-step: finding a service

  1. Enter your query. Type the job, category, or protocol into the search box and submit. The result count updates — the index currently holds 5,379 sites.
  2. Scan the result cards. Each listing shows the service name, a short description, its domain, and a row of signal tags such as llms.txt, ai-plugin, OpenAPI, API, AI bots, Schema.org, and MCP.
  3. Read the score. Every site carries a 0–100 agent-readiness score. The average across indexed sites is 38. A score of 100 appears alongside point breakdowns like +25 llms.txt and +20 ai-plugin, so you can see which signals earned the points.
  4. Open the service if the score and signals match what your agent needs.

Expected result: a filtered list of services ranked by readiness, each with the evidence you need to decide whether an agent can consume it.

Browsing without a query

If you don't have a specific task in mind, use the category entry points instead of the search box:

  • Top 100 — highest-scoring agent-ready sites
  • Newest — recently indexed services
  • MCP Servers — services exposing a Model Context Protocol interface
  • AI Tools, Developer, Data, Finance, E-Commerce, Productivity, Security, Health

These let you survey the landscape before narrowing down.

Reading a result card

Element What it tells you
Score (0–100) Overall agent-readiness
Point breakdown (+25 llms.txt, +20 ai-plugin) Which signals contributed
Signal tags Protocols and formats the site supports
Category label Where it sits in the index
Description What the service does

A site tagged with llms.txt, OpenAPI, MCP, and Schema.org is discoverable and callable through several machine-readable paths. A site with only API gives your agent less to work with.

Common sticking points

  • A high score doesn't mean the service fits your task. Readiness measures machine-consumability, not whether the API does what you need. Check the description and category.
  • Protocol tags are not interchangeable. If your agent speaks MCP, filter for MCP rather than assuming an OpenAPI listing will work.
  • Ranking is readiness-based. A service can't buy a higher position, so treat the order as a signal-quality ranking rather than a popularity or quality ranking.

Related questions

  • What are the 7 agentic signals Not Human Search scores?
  • How Not Human Search ranks sites — and whether payment affects placement
  • What is Not Human Search?