Tool search 164,478 tools · 10,067 live servers

Tech and research event signals: emerging technology events bootstrap data from curated research feeds.

Search open global public-procurement opportunities through the canonical Pro route.

Search Google Flights for real-time flight options between two airports on a specific date.

Search Google Flights date-grid pricing across a date range.

Semantic search over WorldMonitor's accumulating store of past intelligence events (Pro), ranked by similarity.

Keyword search over the COTAL build log (blog posts) and the key documentation and site pages. Returns ranked results with canonical and markdown URLs. Use it to find the page that answers a question before reading it.

Returns one build-log post as markdown (title, summary, date, author, full body) by its slug. Get slugs from cotal_list_posts or cotal_search.

Finds operators whose operating signature most resembles yours. Takes 4 pillars or a codename, computes your signature, then searches the live leaderboard for the nearest neighbors by signature distance. Returns: nearest operators, similarity %, where they outperform you, where you outperform them, and what separates you from the better operator. Makes the leaderboard feel like a network, not a list.

Get the seat map for a flight from our database. Shows all seats, cabin classes, characteristics, and availability as both text and an interactive visual seatmap. Returns cached data — for fresh/updated data, use search_flight (sign in via OAuth).

Search for a flight and get fresh seatmap data. Requires a signed-in account — connect this server to sign in via OAuth. Paid plan users can fetch new flights not yet in our database. Uses a search credit. Returns an interactive seatmap with the results.

Create a seat alert that notifies you by email when a matching seat becomes available on a specific flight. Supports preferences like window, aisle, exit row, specific seat, adjacent seats, and class availability. Requires authentication. The flight must already be in our database — use search_flight first if not.

The exact answer each engine gave to each tracked buyer question in the latest deep measurement for areyoufoundbyai.com: engine, model, date, whether this business was named and on how many samples, live web search or model memory, the competitors named in that answer, the web searches the engine ran before answering (fan-out), and the question's Google demand. This is the receipt behind every score. Filter by a question substring or an engine; answers are trimmed to `chars` characters.

Returns how much of this site sits in Bing's index and how cleanly Bing's crawler gets in, when the owner has connected Bing Webmaster Tools. Bing's index is what ChatGPT search reads today (Microsoft Copilot too), so this is the closest measurable answer to "can AI search find this site": pages in the index (daily trend), pages crawled, crawl errors, robots.txt blocks as Bing sees them, plus conflicts between Bing's view and the site's declared policy. Returns connected=false when no key is connected.

Returns whether Google's index holds this site's pages, when the owner has connected Google Search Console. Google's index is what AI Overviews, AI Mode and Gemini grounding read — the Google counterpart of "Bing's index is what ChatGPT search reads". Three tiers share Google's 2,000-inspections/day budget (there is no bulk index report): a WATCHLIST (homepage, busiest pages, newest posts — every answer in rows) checked daily; PROMOTED PROBLEMS — pages any check found unhealthy join the daily check (stalest first, capped at watched.promotedDaily) until they heal; and a WHOLE-SITE ROTATION walking every published URL in daily slices — healthy pages become the site counts, every problem (watched or not) appears in site.problems, and a page that just healed announces in site.healed for about two days before going quiet. On sites small enough the rotation covers everything every day; site.cycleDays states the honest cadence. site.problems ships a bounded, every-bucket share of the problem rows; to walk ALL of one state's pages, pass problemsState (a stateKey) and page with problemsPage — site.problems then holds exactly that page of 50, in a stable order, while every count stays complete (pages = ceil(site.problemStates[state] / 50)). Presence only, no traffic (read-search-performance has the traffic). Returns connected=false with empty rows when no key is connected.

Returns what classic search actually sent this site over the reported window: total times shown, visits, click rate and impression-weighted average rank, plus the top searches people used and the top pages they landed on. Numbers are the engine's own — Google Search Console and/or Bing Webmaster Tools, whichever the owner connected — never estimated, and never blended (the two count different searchers). Use it to answer "how is this site doing in search?". Returns source="" when no engine has reported yet. When source="bing", totals come from Bing's site-wide daily series (sample sums until that series has reported) while topQueries and topPages are its top-N sample counted separately — the lists sum to less than the totals, and one busy page can even out-count a tile. Neither is an error: state the split rather than reconciling the numbers.

Returns the pages that already rank in classic search but under-earn — the worklist behind the Search Opportunities card (Visibility → Search). Two groups: "almostThere" (ranking 8–20, one improvement from page one) and "seenNotClicked" (already on page one, but a click rate well under THIS site's own page-one median — never an industry benchmark). Each page carries its searches, its totals, and whether it qualified on a single search or on the page's combined demand. Pair it with write-description / update-content to act on what it finds. Returns state "not_connected", "collecting" or "too_thin" when no honest verdict is possible.

Finds images and other attachments ALREADY in this site's media library, so an agent can name one by id — most often as the featured_image on create-content or update-content, which accepts an attachment id but had no way to discover one. Searches titles, captions and descriptions AND alt text (alt is where photographs are usually described — a file called IMG_4831.jpg may carry the alt "sunrise over the river", and a title-only search would miss it). An empty query returns the most recent uploads, which is the right way to ask "what is in here?". Returns each attachment's id, title, alt, url, mime type, pixel dimensions and upload date — the url so a client that can see images may look before it chooses, the dimensions because a 300px logo is not a featured image. READ-ONLY: it uploads nothing and changes nothing. To bring in a picture the library does not have, pass an http(s) image URL as featured_image instead and the write tools import it. There is deliberately no way to upload bytes through this server.