WhatAreYouBuilding.AI

Fetch the full text of one directory record by an id returned from search. Ids are prefixed to say which collection they belong to: "product:<id>" or "community:<id>". Call this after search, on the ids it returned, when the lightweight result is not enough to answer the question. It is the second half of the search/fetch pair that deep-research clients expect. Do not call it with an id you constructed yourself or took from a URL — use get_product or get_community for those, which take a bare id and return structured fields instead of text. Prose in, prose out: this returns a readable record, not a typed object.

Retrieve one community by its directory id, including its join link, platform, region, topic and member count where one was given. Call this to answer a specific question about one group, or after search_communities when a shortlist needs the join links filled in. Do not call it to discover communities: it takes an id and nothing else. Search first. An unknown id returns not-found rather than a guess.

Rank products by engagement on the directory — upvotes, outbound clicks, impressions, shares or verified backlinks — optionally narrowed to one region or category to get a sub-league. Call this for any question about relative standing: what is getting attention, what is doing well in a country or category, what to look at first in an unfamiliar segment. Two orderings, and they answer different questions. sort=score (the default) ranks on the lifetime counter and answers "what is biggest" — it is stable, and a listing collecting clicks for six months outranks one that arrived on Tuesday. sort=movers ranks on clicks gained during the LAST COMPLETED WEEK and answers "what is happening"; it is the only view where something new can be first, and it is the right call for "what is rising", "what is new", or "what changed this week". Be careful what you claim from it. This is attention on this directory and nothing else — not revenue, not users, not growth, and not a judgement about quality. MRR is never a ranking axis here. A product can rank highly because it was interesting to click on. Nothing on this board is bought: no badge, streak or payment moves a listing up it. The movers board describes the week that closed last Sunday, not the last seven days, and the `week` field in the response names it — do not report it as live. Listings with no reading a week ago are not in it at all; the `unmeasured` count says how many that was. metric=backlinks is different in kind from the browsing axes: it ranks people who link back to their listing from their own site, scored on the traffic that link actually sent (stats.referrals) and counted only where our crawler independently found the link. Use it for "who is actually promoting their listing" rather than "who is getting attention here". A listing with referrals but backlink.verified false scores zero on it. Do not call it to filter or find products by their attributes; that is search_products. The board is empty until real engagement accumulates, and an empty board means no traffic yet, not that no products exist.

Retrieve one product by its directory id, with full builder attribution, links, funding state and engagement stats. Returns strictly more per record than a search result: the builder's own accounts and the product's, the website, the city, opt-in MRR where the builder published one, and all-time clicks and impressions. Call this to answer anything specific about a single product — how to reach the builder, where they are, whether they are raising, what the listing actually claims — and call it once per product after a search when a shortlist needs filling out. Do not call it to discover products: it takes an id and nothing else, so it cannot answer "find me X". Search first. Ids are the slug in the product URL, not the display name. An unknown id returns not-found rather than a guess.

List every region, category, funding stage and platform that currently has listings, with counts. Call this before the first search of a conversation, and whenever a filter value is in doubt. The vocabularies are closed and curated — a region or category that is not on this list matches nothing, and an empty result from a guessed filter is indistinguishable from a genuinely empty directory. The counts are also the fastest way to see the shape of the directory: which markets are represented, where the listings actually are, and which filters are worth offering someone. Takes no arguments and is cheap. There is no reason to avoid calling it.

Search across both products and communities at once, returning lightweight results — id, title, url — for retrieval with fetch. Call this when you do not know which collection the answer lives in, or when you are a deep-research client that expects the conventional search/fetch pair. It is deliberately thin: it is the discovery half, and fetch is the other half. Do not call it when you already know you want products or communities specifically — search_products and search_communities take real filters (region, category, funding stage, raising status, platform) and return structured fields instead of prose, which is almost always the better answer. Ids come back prefixed as "product:<id>" or "community:<id>"; pass them to fetch unchanged.

Search builder communities — the Slack workspaces, WhatsApp groups and meetups that independent builders actually gather in — by free text, region, topic and platform. Each result carries a real join link. Call this when someone wants to reach a scene rather than a person: where founders in a given country talk to each other, which group covers a topic, where to go to meet builders in a region. Do not call it to find products or their builders — that is search_products. Communities and products are separate records; a community is a group of people, not something someone shipped. Member counts appear only where the organisers stated one, so a null count means unknown, not small.

Search the directory of builder products. Filter by free text, region, category, funding stage, whether the builder is actively raising, and what they are open to. Returns the matching products with their builder attribution and engagement stats. Call this whenever someone wants to find products or the people behind them by any of those axes — "who is building fintech in Nigeria", "indie AI tools whose founders are raising", "what has this person shipped". It is the right tool for deal sourcing and scouting: raising_status and open_to together answer "who wants to hear from an investor", and region is the axis this directory is organised around. Do not call it to rank or compare products by traction — that is get_leaderboard. Do not call it when you already hold a product id; get_product returns more per record. Funding is opt-in: funding_stage may be "undisclosed" and actively_raising may be null, both meaning the builder declined to say rather than that the answer is no.

Add a product to the directory on behalf of the builder whose agent token this call carries. Call this when the person you are working for has asked to be listed here, or has asked you to add a product they built. Do not call it to add somebody else's product, and do not call it speculatively — a listing is a public claim about a real builder. REQUIRES A TOKEN: send `Authorization: Bearer wayb_…`. A builder creates one at /mine while signed in; without it this tool refuses and every other tool here still works. The listing is created as PENDING and is reviewed before it appears — a successful call returns an id and a status of "pending", never a live listing. Do not report it as published. Submit the builder's OWN product. A builder can list more than one product, but the directory refuses a second copy of a product it already lists (by website host or by name) with a message saying so. Call list_filters first: category and region are closed vocabularies, listed in full under products.accepted_values, and a value outside them is rejected rather than corrected. Funding fields are optional and tri-state — omit activelyRaising, or send null, where the builder has not said. Do not infer it, and do not send false to mean "did not say".