ProgrammableMarketing/orthogonal.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 10
  • Big bets · 3
  • Wildcards · 2
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Orthogonal
Orthogonal logo

growth playbook · Nov 10, 2026

orthogonal.com (opens in a new tab)

Orthogonal growth playbook

Diagnosis

Orthogonal (YC W26, $4.3 million seed led by Pantera) has grown its catalog fast, from 35+ APIs in June to 87 APIs and 1,774 endpoints today, and is hiring its first Growth Lead to take revenue past the 0-to-1 phase.

The catalog has outgrown the way it is organised and described: 62 of 87 APIs sit in "Uncategorized", the llms.txt file that agents read indexes only 59 of them and sends providers to a guide that returns 404, and the company's own pages give five different sizes for the catalog.

This playbook fixes discovery first (categories, llms.txt, category pages, one live count), adds proof and a clearer first dollar, then answers the problem the founders named themselves, API selection, with public call, latency and success data per listing, budget alerts, a provider co-marketing loop and, as big bets, budgeted provider selection and a vertical beyond go-to-market data.

Growth Score

7/10

Biggest Opportunity

Become the place agents and their builders choose which API to call: a fully organised catalog with real usage, speed and success data, which no tool directory or app-connector rival shows today.

Biggest Risk

Agent tooling is crowded (Composio, Smithery and providers selling direct), and a catalog that grows faster than it is organised makes Orthogonal look smaller and harder to use than it is, just as the company hires for growth.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Put the 62 "Uncategorized" APIs into categories, so the catalog's 14 categories show the whole catalog

    Export the 62 uncategorized APIs and tag the ten most called first.

    High impact First result in 2 weeks
  2. 2

    Generate llms.txt from the catalog: it indexes 59 APIs, the catalog has 87

    Diff the 59 indexed APIs against the 87 in the catalog.

    High impact First result in 2 weeks
  3. 3

    Make the 14 category pages indexable landing pages for "<task> API for agents" searches

    Add the 14 category URLs to the sitemap.

    High impact First result in 1 month

02

Your idea portfolio

22 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 2Big bets · 10Fill-ins · 8Reconsider · 2
Effort →

Showing 22 of 22 ideas

This week 7

Quick wins with a clear first action.

  • 01

    The homepage invites visitors to "Explore all 14 categories", but 62 of the catalog's 87 APIs (71%) sit under "Uncategorized". The category pages therefore show only a slice of what Orthogonal sells: Search lists 2 APIs while Serper, a Google Search API, is uncategorized; Email Finder lists 4 while Icypeas and Leadsforge, both email and lead tools, are uncategorized; Browser Automation lists 2 while TinyFish, which the blog featured on September 23 as browser automation, is uncategorized. Olostep, one of the first cards on the "Most called" view, has no category at all. A developer or an agent browsing by task sees a catalog roughly a third of its real size.

    High impactLow effort First result in 2 weeks Growth Lead

    First action

    Export the 62 uncategorized APIs and tag the ten most called first.

    How to measure it

    Categorised APIs

    Now
    –
    Target
    100% of the catalog, and +20% catalog-to-first-call conversion
    By
    30 days

    Steps

    1. 1

      Export the list

      All 62 APIs under /catalog/uncategorized, with call counts.

      Senior Software Engineer 2 hours

    2. 2

      Extend the categories

      Add the handful of categories the catalog now needs, and merge near-duplicates such as Search and AI Search if they confuse.

      Growth Lead 1 day

    3. 3

      Tag the top ten

      Start with the most called: Olostep, Serper, Icypeas, Leadsforge, TinyFish and the next five.

      Growth Lead 1 day

    4. 4

      Tag the rest

      One primary and up to two secondary categories each.

      Growth Lead 3 days

    5. 5

      Require a category

      Make it a required field in provider onboarding and in the review step.

      Senior Software Engineer 1 day

    6. 6

      Check agent search

      Run category queries over MCP and REST and confirm the tagged APIs come back.

      Co-founder & CTO 1 day

    7. 7

      Measure

      Category page visits to first call, before and after.

      Growth Lead monthly

    First result
    2 weeks
    Cost
    About a week of staff time
    Owner
    Growth Lead

    Smallest test

    Tag Serper, Icypeas, Leadsforge, TinyFish and Olostep today and watch their category page traffic.

    Why it works

    Assign every uncategorized API to one primary and up to two secondary categories, add the few categories the catalog now needs (for example Social Data, Verification, Voice and Phone, Financial Data, Jobs Data, Compute), and make a category required in provider onboarding so the count never drifts back. Then check that the MCP and REST search return the newly tagged APIs for category queries, and that each category page links to all of them.

    Most buyers, human or agent, start from a task (find an email, search the web), not a brand name. Today the best-known APIs for several tasks are invisible from the task pages, so the catalog undersells itself and pushes visitors to rivals that look bigger. Tagging is a one-week job with no engineering risk, and it improves every later idea that relies on categories (category landing pages, comparisons, selection).

    Ready to use

    ChecklistCatalog categorisation checklist

    [ ] Serper -> Search (and Web Data)
    [ ] Icypeas -> Email Finder (and People Data)
    [ ] Leadsforge -> People Data (and Email Finder)
    [ ] TinyFish -> Browser Automation (and Web Data)
    [ ] Olostep -> Web Data (and Scrape)
    [ ] Scrape Creators -> new Social Data category
    [ ] Abstract -> Identity Verification
    [ ] Company Enrich -> Company Data
    [ ] Remaining 54 APIs tagged
    [ ] Category required in onboarding
    [ ] MCP and REST category search checked
    [ ] Uncategorized count at 0

    Risks and how to handle them

    • Too many small categories

      Cap at about 20 and use secondary tags for the long tail.

    • Providers disagree with their category

      Let them suggest a change during review.

    Evidence

    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • Your website/catalog/uncategorized ("page 1 of 8", checked twice on November 10, 2026) lists Olostep, Icypeas, Serper (a Google Search API for web, image, video, news, maps, shopping and scholar results), Leadsforge, TinyFish (AI-driven browser automation and web search), Company Enrich, Scrape Creators and Abstract. Olostep, Icypeas and Serper are among the first cards on the "Most called" catalog view with no category tag, while the Search category shows 2 APIs, Email Finder 4 and Browser Automation 2.Source
    • Your websiteHomepage (checked November 10, 2026): H1 "Get your agent the data it needs."; "Access data and services through one connection. Pay for the calls you make, without a separate subscription to each provider."; "87 APIs" and "1,774 endpoints"; "Explore all 14 categories"; per-call prices from "$0.002" to "from $0.50"; CTAs "Explore APIs", "Connect an agent", "Get your API key" and "Book a call"; no testimonials, customer logos or customer results on the page.Source
    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
  • 02

    Orthogonal lets providers list "through your own AI agent" over MCP, and the file agents read, llms.txt, points them to "List your API: https://www.orthogonal.com/docs/list-your-api". That URL returned 404 Not Found on two checks, and it is not in the sitemap. A provider who asks their agent to list their API hits a dead end at the first step.

    Medium impactLow effort First result in 1 week Senior Software Engineer

    First action

    Redirect /docs/list-your-api to the live listing guide.

    How to measure it

    Listing requests started

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Redirect

      Point /docs/list-your-api at the live guide, or publish it there.

      Senior Software Engineer 1 hour

    2. 2

      Add to sitemap

      So search and agents find it.

      Senior Software Engineer 1 hour

    3. 3

      Link check

      Fail the build on broken links in llms.txt, skill.md and docs.

      Senior Software Engineer 1 day

    4. 4

      Test the agent path

      Ask an agent to list a test API from llms.txt alone.

      Co-founder & CTO 2 hours

    5. 5

      Track

      Listing requests by source: dashboard, agent, call.

      Growth Lead weekly

    6. 6

      Review monthly

      Check every agent-facing file for drift.

      Senior Software Engineer monthly

    First result
    1 week
    Cost
    $0
    Owner
    Senior Software Engineer

    Smallest test

    Add the redirect today and run the agent listing flow once.

    Why it works

    Publish the guide at that URL (or redirect it to the current guide), add it to the sitemap, and add a link check to the build that fails when llms.txt, skill.md or the docs link to a missing page.

    Supply is half of a marketplace, and the agent-led listing path is a differentiator only if it works end to end. A redirect is minutes of work.

    Risks and how to handle them

    • Other agent-facing links break later

      Keep the build-time link check.

    Evidence

    • Your websitellms.txt (checked November 10, 2026): indexes 59 per-API skill files against 87 APIs in the catalog (TinyFish, featured in a September 23 partner post, is not in it); it points providers to "List your API: https://www.orthogonal.com/docs/list-your-api", which returned 404 Not Found on two checks that day; it mentions a one-time $1 starter credit and that "Top-up packages carry a 5% processing fee".Source
    • Your websiteSell page: "Reach developers and AI agents with your API."; listing is "Free" with no monthly minimum; providers "set your provider price" and marketplace pricing terms are shared in the onboarding workspace after approval; payouts for the previous month are "initiated on the 15th (UTC)"; five-step onboarding with the Orth onboarding agent; a "Get verified" link with no stated requirements; no buyer or call statistics.Source
    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
  • 03

    llms.txt indexes 59 per-API skill files, while the catalog lists 87 APIs and the sitemap has 85 skill.md files. TinyFish, the subject of the latest partner spotlight, is not in the index. An agent that reads llms.txt to decide what Orthogonal can do never learns about roughly a third of the catalog, including some of the newest partners.

    High impactLow effort First result in 2 weeks Senior Software Engineer

    First action

    Diff the 59 indexed APIs against the 87 in the catalog.

    How to measure it

    llms.txt coverage

    Now
    –
    Target
    100% of catalog APIs
    By
    2 weeks

    Steps

    1. 1

      Diff

      List the APIs missing from the index.

      Senior Software Engineer 1 hour

    2. 2

      Generate

      Build llms.txt from catalog data at deploy.

      Senior Software Engineer 1 day

    3. 3

      Add metadata

      Category and from-price per entry.

      Senior Software Engineer 1 day

    4. 4

      Count test

      Fail the build if counts differ.

      Senior Software Engineer 2 hours

    5. 5

      Tell providers

      Let newly indexed partners know they are now agent-discoverable.

      Growth Lead 1 day

    6. 6

      Watch calls

      Calls to newly indexed APIs over 30 days.

      Growth Lead monthly

    First result
    2 weeks
    Cost
    Two engineering days
    Owner
    Senior Software Engineer

    Smallest test

    Add the missing APIs by hand today; automate next week.

    Why it works

    Build llms.txt and skill.md from the same catalog data the site uses, at deploy time, with each API's categories and from-price, and list the machine-readable /discover and /openapi.json endpoints at the top. Add a test that the count in llms.txt equals the catalog count.

    For an agent-first product, llms.txt is the storefront. Keeping it generated means every new provider is discoverable by agents on day one, which is also what providers are paying attention to.

    Risks and how to handle them

    • File grows too long for agents

      Keep one line per API and link to per-API skill files.

    Evidence

    • Your websitellms.txt (checked November 10, 2026): indexes 59 per-API skill files against 87 APIs in the catalog (TinyFish, featured in a September 23 partner post, is not in it); it points providers to "List your API: https://www.orthogonal.com/docs/list-your-api", which returned 404 Not Found on two checks that day; it mentions a one-time $1 starter credit and that "Top-up packages carry a 5% processing fee".Source
    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
  • 04

    The catalog says 87 APIs and 1,774 endpoints. The seed post says more than 35 APIs, the Show HN post 50+ providers and 700+ endpoints, the about page "dozens of verified providers", and the YC profile hundreds of APIs. AI assistants and journalists summarising Orthogonal pick one of these at random, usually an old, smaller one.

    Medium impactLow effort First result in 1 month Growth Lead

    First action

    Replace "dozens of verified providers" on the about page with the live count.

    How to measure it

    Consistent count coverage

    Now
    –
    Target
    All owned pages and profiles
    By
    2 weeks

    Steps

    1. 1

      List the claims

      Every page and profile that states a size.

      Growth Lead 2 hours

    2. 2

      Make it live

      One shared component for counts on owned pages.

      Design Engineer 1 day

    3. 3

      Update profiles

      YC, LinkedIn and X bios.

      Founder/CEO 1 hour

    4. 4

      Add the growth line

      From 35+ to 87 APIs since June.

      Growth Lead 1 hour

    5. 5

      Date old posts

      "At the time of writing" notes on the seed and launch posts.

      Growth Lead 1 hour

    6. 6

      Check assistants

      Ask a few assistants how big the catalog is, monthly.

      Growth Lead monthly

    First result
    1 month
    Cost
    $0
    Owner
    Growth Lead

    Smallest test

    Fix the about page and YC profile today.

    Why it works

    Pull the live API and endpoint counts into the homepage, about page, sell page and llms.txt from the catalog, update the YC profile to the current number, and add a short "catalog growth" line (35+ in June, 87 in November) as a proof point. Date-stamp counts in older posts rather than editing history.

    Growth is the story investors, providers and buyers want to hear, and a consistent, rising number tells it. It also stops assistants describing Orthogonal as smaller than it is.

    Risks and how to handle them

    • Counts drop when APIs are delisted

      Show endpoints and APIs together; both are honest.

    Evidence

    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • Your websiteSeed announcement (June 25, 2026): $4.3 million led by Pantera Capital, with Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound and Surreal by Premise; "already live in production" with GTM teams and AI-native startups; more than 35 APIs at the time, including Apollo, People Data Labs and Coresignal; fiat, x402 and MPP payment rails; the money funds "expansion of Orthogonal's engineering and go-to-market teams".Source
    • Hacker NewsShow HN (September 1, 2026, 12 points, no comments): "one integration to discover, access, and pay for APIs" with 50+ providers and 700+ endpoints; it started with go-to-market APIs and is expanding; "The problem we're working on now is API selection", choosing providers by price, latency, reliability and result quality; the founders ask whether people would trust an agent with a budget to choose its own API provider.Source
    • Y CombinatorYC profile: Winter 2026, team size 2, "APIs weren't built for agents. Orthogonal fixes that.", and agents can discover, access and pay for hundreds of APIs; Orthogonal's own about page says it "connects dozens of verified providers".Source
  • 05

    The catalog already has category URLs (/catalog/email-finder, /catalog/web-search, /catalog/people-search and so on), but none are in the sitemap, which lists 85 provider pages and 59 blog posts. Developers search by task ("email finder API", "web search API for agents"), and the category page is the natural answer: several providers, prices side by side, one key.

    High impactMedium effort First result in 1 month Growth Lead

    First action

    Add the 14 category URLs to the sitemap.

    How to measure it

    Category page organic sessions

    Now
    –
    Target
    1,000 a month
    By
    90 days

    Steps

    1. 1

      Sitemap

      Add all category URLs.

      Senior Software Engineer 1 hour

    2. 2

      Match names

      Align category labels and slugs.

      Senior Software Engineer 1 day

    3. 3

      Write intros

      Task, price range, how to call.

      Growth Lead 1 week

    4. 4

      Design the template

      Provider table with from-prices.

      Design Engineer 3 days

    5. 5

      Link internally

      From provider pages and blog posts.

      Growth Lead 2 days

    6. 6

      Measure

      Search Console by category.

      Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Growth Lead

    Smallest test

    Index and write up Email Finder first.

    Why it works

    Add every category page to the sitemap, give each a task-led title and description, a short intro, the price range across providers, a one-line MCP example and links to the providers in it. Fix label and URL mismatches (Company Data lives at /catalog/company-search, Web Data at /catalog/web-search) so titles match what people search.

    Category pages answer the comparison searches that single-provider pages and partner posts cannot, and a marketplace is the only kind of site that can honestly show several rivals on one page.

    Risks and how to handle them

    • Thin pages

      Only index categories with three or more APIs after idea 1.

    Builds on

    Evidence

    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • HiringGrowth Lead (San Francisco, in person, 5+ years): help with "accelerating revenue growth beyond the '0-to-1 phase'", build GTM strategy with the founders "to hit our revenue targets", run multi-channel demand generation, design A/B tests to improve conversion rates, research audiences and competitors, and measure performance.Source
  • 06

    The homepage has no testimonials, customer logos or results. Yet Orthogonal has a published, specific outcome: Breaknine surfaced 622 updates from 233 source domains in two weeks, with 539 of 622 (about 87%) independently grounded, against close to zero before. The seed post says Orthogonal is live in production with GTM teams and AI-native startups.

    Medium impactLow effort First result in 3 weeks Growth Lead

    First action

    Write a two-line Breaknine proof block for the homepage.

    How to measure it

    Homepage-to-key conversion

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Write the block

      Numbers, one sentence, link.

      Growth Lead 1 hour

    2. 2

      Design it

      A proof strip under the hero.

      Design Engineer 1 day

    3. 3

      A/B test

      With and without the strip.

      Growth Lead 3 weeks

    4. 4

      Ask for more

      Three production customers for a short quote.

      Founder/CEO 2 weeks

    5. 5

      Add logos

      Where customers agree.

      Growth Lead ongoing

    6. 6

      Reuse

      On /sell and in outreach.

      Growth Lead 1 day

    First result
    3 weeks
    Cost
    $0
    Owner
    Growth Lead

    Smallest test

    Add the strip and compare key creation for two weeks.

    Why it works

    Add a proof strip under the hero with the Breaknine numbers and a link to the case study, then collect two or three more short results (time saved per integration, providers swapped without code changes) from production customers who agree to be named.

    Developers trust specific numbers from a similar team more than claims. One result also answers the unspoken question for a seed-stage marketplace: does anyone use this in production?

    Risks and how to handle them

    • Grounding metric is unfamiliar

      Explain it in plain words: evidence from a source other than the company itself.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): H1 "Get your agent the data it needs."; "Access data and services through one connection. Pay for the calls you make, without a separate subscription to each provider."; "87 APIs" and "1,774 endpoints"; "Explore all 14 categories"; per-call prices from "$0.002" to "from $0.50"; CTAs "Explore APIs", "Connect an agent", "Get your API key" and "Book a call"; no testimonials, customer logos or customer results on the page.Source
    • Your websiteBreaknine case study (August 4, 2026): a tool that turns venture investors' CRM data into outreach moved its news discovery onto Orthogonal, using Fiber AI, Apollo, Serper, Bytemine, Company Enrich, PredictLeads, Fundable and Aviato; in its first two weeks it surfaced 622 updates from 233 source domains, and 539 of 622 (about 87%) were independently grounded, against "close to zero" before.Source
    • Your websiteSeed announcement (June 25, 2026): $4.3 million led by Pantera Capital, with Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound and Surreal by Premise; "already live in production" with GTM teams and AI-native startups; more than 35 APIs at the time, including Apollo, People Data Labs and Coresignal; fiat, x402 and MPP payment rails; the money funds "expansion of Orthogonal's engineering and go-to-market teams".Source
  • 07

    New agent accounts get "a one-time $1 starter credit", and prices run from $0.001 to over $1 a call. At Apollo's $0.002 People Search, $1 is 500 searches; at $0.01 enrichment it is 100 lookups; at a $0.50 search it is two calls. Nobody sees that translation, so $1 sounds small and new users don't know which first task will succeed within it.

    Medium impactLow effort First result in 2 weeks Growth Lead

    First action

    Pick five reliable tasks under $0.05 each.

    How to measure it

    First-call success rate

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Pick tasks

      Five cheap, reliable, useful calls.

      Growth Lead 1 day

    2. 2

      Write prompts

      One copy-paste prompt per task.

      Growth Lead 1 day

    3. 3

      Add to the dashboard

      A first-run panel.

      Design Engineer 2 days

    4. 4

      Add to agent signup

      Return the menu in the signup response.

      Senior Software Engineer 1 day

    5. 5

      Track

      First task to top-up rate.

      Growth Lead weekly

    6. 6

      Rotate

      Swap tasks that don't convert.

      Growth Lead monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Growth Lead

    Smallest test

    Email the menu to last month's signups who never called.

    Why it works

    On signup, in the dashboard and in the agent signup response, show a "what $1 gets you" menu of five tasks with exact costs and a copy-paste prompt for each, chosen from cheap, reliable endpoints. Track which first task leads to a top-up.

    A concrete first win inside the free credit is the fastest path to the first top-up, and it steers new users away from expensive endpoints that would drain the credit in one call.

    Risks and how to handle them

    • Users only use cheap endpoints

      Show one premium task as the next step after the first top-up.

    Evidence

    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
    • Your websiteApollo listing: "Verified", "9 endpoints" priced $0.0020 to $0.0500 per call, a "skill.md (for agents)" link, SDK and CLI quickstart, "More in Company Search" related APIs and a "Get your key" button; no call counts, latency, uptime, reviews or comparison with buying from the provider directly. The sitemap lists 85 publisher pages like it.Source
    • Your websiteHomepage (checked November 10, 2026): H1 "Get your agent the data it needs."; "Access data and services through one connection. Pay for the calls you make, without a separate subscription to each provider."; "87 APIs" and "1,774 endpoints"; "Explore all 14 categories"; per-call prices from "$0.002" to "from $0.50"; CTAs "Explore APIs", "Connect an agent", "Get your API key" and "Book a call"; no testimonials, customer logos or customer results on the page.Source

This quarter 10

The core plays for the next three months.

  • 08

    The founders say the problem they are working on now is API selection: price, latency, reliability and result quality. Orthogonal already sees every call, yet listings show only a "Reliable" badge and a from-price, and the "Most called" sort hides the numbers behind it. No rival directory shows this either.

    High impactMedium effort First result in 1 quarter Co founder & CTO

    First action

    Compute the three numbers for the top 20 APIs from call logs.

    How to measure it

    Category-to-call conversion

    Now
    –
    Target
    +20%
    By
    1 quarter

    Steps

    1. 1

      Compute

      Calls, latency and success per API.

      Co-founder & CTO 1 week

    2. 2

      Preview with providers

      Two weeks to review before publishing.

      Founder/CEO 2 weeks

    3. 3

      Design

      Stats on cards and a comparison table.

      Design Engineer 1 week

    4. 4

      Build

      Pages plus MCP and REST fields.

      Senior Software Engineer 2 weeks

    5. 5

      Define the badge

      Tie "Reliable" to a published threshold.

      Co-founder & CTO 1 day

    6. 6

      Measure

      Conversion and provider feedback.

      Growth Lead monthly

    First result
    1 quarter
    Cost
    About three engineering weeks
    Owner
    Co founder & CTO

    Smallest test

    Add latency and success to the Email Finder category only.

    Why it works

    Show 30-day calls (or a usage band), median and p95 latency, and success rate on each provider page and in a side-by-side table on each category page, and return the same fields in the MCP and REST search so agents can choose. Let providers see their own figures first, then publish.

    Real performance data turns the catalog into a decision tool, gives good providers a reason to promote their listing, and is an asset rivals cannot copy without the call volume.

    Risks and how to handle them

    • Providers object to low scores

      Preview first and publish bands rather than raw numbers for small samples.

    Builds on

    Evidence

    • Hacker NewsShow HN (September 1, 2026, 12 points, no comments): "one integration to discover, access, and pay for APIs" with 50+ providers and 700+ endpoints; it started with go-to-market APIs and is expanding; "The problem we're working on now is API selection", choosing providers by price, latency, reliability and result quality; the founders ask whether people would trust an agent with a budget to choose its own API provider.Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • Your websiteApollo listing: "Verified", "9 endpoints" priced $0.0020 to $0.0500 per call, a "skill.md (for agents)" link, SDK and CLI quickstart, "More in Company Search" related APIs and a "Get your key" button; no call counts, latency, uptime, reviews or comparison with buying from the provider directly. The sitemap lists 85 publisher pages like it.Source
    • Competitor researchRivals' homepages: Composio, "Give your AI secure access to 1,700+ apps in minutes", with a free Hobby plan of 100,000 tool calls a month and some tools billed per call; Smithery, "Connect agents to thousands of tools and services. Auth, credentials, and sessions handled for you."; OpenRouter, the model gateway Orthogonal's founders compare it to, publishes public rankings of usage by tokens processed.Source
  • 09

    Orthogonal sees what agents actually call across 87 APIs, and its catalog already sorts by "Most called" without showing the numbers. Model gateways have shown that a public usage ranking becomes a reference that builders check and press quote. Nobody publishes this for data and service APIs.

    High impactMedium effort First result in 1 month Growth Lead

    First action

    Pull last month's top 20 by calls and check that no customer can be identified.

    How to measure it

    Links to the index

    Now
    –
    Target
    30 referring domains
    By
    2 quarters

    Steps

    1. 1

      Define the rules

      What counts, minimum sample, bands.

      Co-founder & CTO 2 days

    2. 2

      Build the page

      Overall, per category, movers, archive.

      Design Engineer 1 week

    3. 3

      Write the notes

      Three short observations each month.

      Growth Lead monthly

    4. 4

      Tell providers

      Ranking and a share card.

      Growth Lead monthly

    5. 5

      Distribute

      X, LinkedIn and developer newsletters.

      Founder/CEO monthly

    6. 6

      Measure

      Links, visits, signups from the page.

      Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Growth Lead

    Smallest test

    Publish one month's top ten as a blog post.

    Why it works

    Each month, publish the top APIs by calls overall and per category, the fastest movers and the newest entries, with anonymised totals or bands. Send it to providers (who will share their ranking), post it on X and LinkedIn, and keep an archive page.

    A recurring, data-led page earns links and mentions that partner spotlights do not, gives providers a reason to promote Orthogonal, and turns usage data into authority.

    Risks and how to handle them

    • Reveals a customer's usage

      Use bands and minimum sample sizes.

    Evidence

    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • Competitor researchRivals' homepages: Composio, "Give your AI secure access to 1,700+ apps in minutes", with a free Hobby plan of 100,000 tool calls a month and some tools billed per call; Smithery, "Connect agents to thousands of tools and services. Auth, credentials, and sessions handled for you."; OpenRouter, the model gateway Orthogonal's founders compare it to, publishes public rankings of usage by tokens processed.Source
    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
  • 10

    Most recent blog posts are partner spotlights organised around a provider (TinyFish, Extruct, Akta, FullEnrich), and the docs list only five use cases. Builders search for the job, not the vendor. Breaknine's news-monitoring setup, which combined eight APIs, is exactly the kind of recipe others want to copy.

    High impactMedium effort First result in 1 month Growth Lead

    First action

    Write the news-monitoring recipe from the Breaknine setup.

    How to measure it

    Recipe-sourced signups

    Now
    –
    Target
    150 a month
    By
    2 quarters

    Steps

    1. 1

      Pick ten tasks

      From call logs and the five docs use cases.

      Growth Lead 2 days

    2. 2

      Build and price

      Run each recipe and record the cost.

      Senior Software Engineer 2 weeks

    3. 3

      Write

      Prompt, code, cost, variations.

      Growth Lead 3 weeks

    4. 4

      Template

      A recipe page design.

      Design Engineer 1 week

    5. 5

      Cross-link

      Categories, providers and docs.

      Growth Lead 1 week

    6. 6

      Promote

      One recipe a week on X and LinkedIn.

      Founder/CEO weekly

    First result
    1 month
    Cost
    Staff time plus test call credits
    Owner
    Growth Lead

    Smallest test

    Publish two recipes and compare signups with two spotlights.

    Why it works

    Publish recipes such as "Monitor news on a list of companies", "Find and verify a work email", "Build an account brief" and "Scrape a site that has no API": the APIs used, a copy-paste MCP prompt, the code, and the measured cost per run (for example per 100 companies). Link each recipe from the matching category page and provider pages.

    Task pages match search intent and show the unique value of a multi-provider catalog: combining sources in one flow with one bill. The cost per run removes the main question before a top-up.

    Risks and how to handle them

    • Costs change with provider prices

      Recompute cost per run automatically each month.

    Evidence

    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
    • Your websiteBreaknine case study (August 4, 2026): a tool that turns venture investors' CRM data into outreach moved its news discovery onto Orthogonal, using Fiber AI, Apollo, Serper, Bytemine, Company Enrich, PredictLeads, Fundable and Aviato; in its first two weeks it surfaced 622 updates from 233 source domains, and 539 of 622 (about 87%) were independently grounded, against "close to zero" before.Source
    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
  • 11

    Orthogonal has 85 provider pages, and each provider has its own developer audience, docs and changelog. The sell page promises "Reach developers and AI agents with your API" but offers providers nothing to promote the listing with, and partner spotlights are published only on Orthogonal's blog.

    High impactMedium effort First result in 1 quarter Growth Lead

    First action

    Ask the five most-called providers to add a docs link.

    How to measure it

    Provider-referred signups

    Now
    –
    Target
    20% of new signups
    By
    2 quarters

    Steps

    1. 1

      Design the kit

      Badge, snippet and share card.

      Design Engineer 1 week

    2. 2

      Referral links

      One tracked link per provider.

      Senior Software Engineer 2 days

    3. 3

      Start with five

      The most-called providers.

      Founder/CEO 2 weeks

    4. 4

      Co-branded recipes

      One per provider.

      Growth Lead ongoing

    5. 5

      Monthly stats

      Calls and new buyers per provider.

      Growth Lead monthly

    6. 6

      Roll out

      Add the kit to onboarding for every new provider.

      Growth Lead 1 week

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Growth Lead

    Smallest test

    One provider adds a docs link; track signups for a month.

    Why it works

    Ship a kit for each provider: a badge and a deep link to their Orthogonal page, a snippet for their docs ("Call us from any MCP client with one key"), a co-branded recipe, and a monthly stats email. Track signups by provider referral link and feature the providers who send the most traffic.

    In a two-sided marketplace the supply side is also a distribution channel. A link from a provider's docs reaches developers who already want that data and makes Orthogonal the easy way to try it.

    Risks and how to handle them

    • Providers fear channel conflict

      Show that Orthogonal brings incremental, per-call buyers they would not sign directly.

    Evidence

    • Your websiteSell page: "Reach developers and AI agents with your API."; listing is "Free" with no monthly minimum; providers "set your provider price" and marketplace pricing terms are shared in the onboarding workspace after approval; payouts for the previous month are "initiated on the 15th (UTC)"; five-step onboarding with the Orth onboarding agent; a "Get verified" link with no stated requirements; no buyer or call statistics.Source
    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
  • 12

    The sell page says listing is free with no monthly minimum, but the revenue terms are only shared "in your onboarding workspace after approval", and "Get verified" links to a section with no requirements. A provider weighing whether to list has to apply before learning what they would earn or what the badge needs.

    Medium impactLow effort First result in 1 month Founder/CEO

    First action

    Write the earnings example for a $0.01 endpoint.

    How to measure it

    Provider applications

    Now
    –
    Target
    +30%
    By
    90 days

    Steps

    1. 1

      Decide what to publish

      Take rate or range, payout rules.

      Founder/CEO 2 days

    2. 2

      Write verification rules

      Checklist and benefits.

      Co-founder & CTO 2 days

    3. 3

      Earnings example

      Per 10,000 calls.

      Growth Lead 1 day

    4. 4

      Update /sell

      Terms, FAQ and example.

      Design Engineer 3 days

    5. 5

      Mirror for agents

      The same terms in llms.txt.

      Senior Software Engineer 1 hour

    6. 6

      Measure

      Applications and approval rate.

      Growth Lead monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founder/CEO

    Smallest test

    Publish the verification checklist first.

    Why it works

    State the marketplace take (or the range), how provider price maps to buyer price, payout method and threshold, and the verification checklist with what the badge gives (placement, the "Verified publisher" label). Add a short FAQ and an earnings example.

    Clear terms raise application rates and shorten the founders' sales calls with providers; verification becomes a goal providers work toward.

    Risks and how to handle them

    • Locks in terms too early

      Publish as current terms with a review date.

    Evidence

    • Your websiteSell page: "Reach developers and AI agents with your API."; listing is "Free" with no monthly minimum; providers "set your provider price" and marketplace pricing terms are shared in the onboarding workspace after approval; payouts for the previous month are "initiated on the 15th (UTC)"; five-step onboarding with the Orth onboarding agent; a "Get verified" link with no stated requirements; no buyer or call statistics.Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
  • 13

    Orthogonal's spend limits are strong: daily caps per account and per key, and allowed-API lists. But when a cap is reached, calls are simply refused with DAILY_ACCOUNT_LIMIT_EXCEEDED or DAILY_KEY_LIMIT_EXCEEDED, and the docs describe no alerts before that happens. An agent in production stops mid-task, and the team finds out from a failure, not a warning.

    High impactMedium effort First result in 1 month Senior Software Engineer

    First action

    Count last month's refused calls by cap type.

    How to measure it

    Budget-refused calls

    Now
    –
    Target
    -50%
    By
    1 quarter

    Steps

    1. 1

      Measure refusals

      By cap type and account.

      Senior Software Engineer 1 day

    2. 2

      Alerts

      Email and webhook at 50/80/100%.

      Senior Software Engineer 1 week

    3. 3

      Remaining budget

      A field in every response, next to priceCents.

      Co-founder & CTO 3 days

    4. 4

      Auto top-up

      Optional, with a monthly ceiling.

      Senior Software Engineer 1 week

    5. 5

      Dashboard

      Near-misses and suggested caps.

      Design Engineer 1 week

    6. 6

      Track

      Refusals and top-ups.

      Growth Lead monthly

    First result
    1 month
    Cost
    About three engineering weeks
    Owner
    Senior Software Engineer

    Smallest test

    Email the 80% warning only, for one month.

    Why it works

    Send email and webhook alerts at 50%, 80% and 100% of each cap and at a low-balance threshold, add an optional auto top-up, and return a "remaining budget" field with each call so agents can plan. Show recent near-misses in the dashboard.

    Usage-based products lose customers when production breaks unexpectedly. Warnings and auto top-up keep agents running and turn a refusal into a top-up.

    Risks and how to handle them

    • Alert fatigue

      Let users pick thresholds and channels.

    Evidence

    • Your websiteSpend limits docs: a daily cap per account or organisation and one per API key, counted since midnight UTC; per-key allowed-API lists ("A call to an API outside either list is refused with HTTP 403"); refusal codes DAILY_ACCOUNT_LIMIT_EXCEEDED and DAILY_KEY_LIMIT_EXCEEDED; no alerts before a cap or a low balance is reached are described.Source
    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
  • 14

    Every response reports its price in priceCents, but the pricing docs do not say whether a call that errors, times out or returns no match is charged. For enrichment and email-finding APIs, empty results are common, and a team handing an agent a budget will ask exactly this.

    Medium impactLow effort First result in 1 month Founder/CEO

    First action

    Check how each of the top 20 endpoints bills empty results.

    How to measure it

    Week-one top-up rate

    Now
    –
    Target
    +10%
    By
    90 days

    Steps

    1. 1

      Audit

      Billing on errors and empty results per endpoint.

      Co-founder & CTO 1 week

    2. 2

      Write the policy

      Short and specific.

      Founder/CEO 1 day

    3. 3

      Flag endpoints

      On listings and in API responses.

      Senior Software Engineer 3 days

    4. 4

      Usage view

      Failed calls and amounts.

      Design Engineer 3 days

    5. 5

      Publish

      On pricing docs and llms.txt.

      Growth Lead 1 hour

    6. 6

      Track

      Support questions about charges.

      Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founder/CEO

    Smallest test

    Add the policy paragraph to the pricing docs this week.

    Why it works

    Write a one-paragraph policy (for example: provider and network errors are never charged; empty results follow the provider's rule, shown on each endpoint) and show a "charged on empty result: yes/no" flag per endpoint. Report failed-call totals in the usage view.

    Trust is the main barrier to giving an agent a wallet. A clear rule removes a common objection in sales calls and makes per-call pricing feel safe.

    Risks and how to handle them

    • Providers bill empty results

      Show the provider's rule rather than absorbing the cost.

    Evidence

    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
    • Hacker NewsShow HN (September 1, 2026, 12 points, no comments): "one integration to discover, access, and pay for APIs" with 50+ providers and 700+ endpoints; it started with go-to-market APIs and is expanding; "The problem we're working on now is API selection", choosing providers by price, latency, reliability and result quality; the founders ask whether people would trust an agent with a budget to choose its own API provider.Source
  • 15

    The homepage promise is "Pay for the calls you make, without a separate subscription to each provider", and Orthogonal's first customers are GTM teams. But no page lets a team enter its monthly volumes (enrichments, email finds, searches) and see the per-call total next to what separate plans would cost.

    Medium impactMedium effort First result in 1 month Growth Lead

    First action

    Choose the five tasks GTM teams run most from call logs.

    How to measure it

    Calculator-to-key rate

    Now
    –
    Target
    15%
    By
    90 days

    Steps

    1. 1

      Pick tasks

      Five most common GTM tasks.

      Growth Lead 1 day

    2. 2

      Price them

      From live catalog prices.

      Senior Software Engineer 3 days

    3. 3

      Design

      Inputs, total, share link.

      Design Engineer 1 week

    4. 4

      Launch

      Linked from homepage and recipes.

      Growth Lead 1 day

    5. 5

      Route big teams

      High totals invite a call.

      Founder/CEO ongoing

    6. 6

      Measure

      Use, keys and calls booked.

      Growth Lead monthly

    First result
    1 month
    Cost
    About two weeks of staff time
    Owner
    Growth Lead

    Smallest test

    A static table of five tasks at three volumes.

    Why it works

    Build a calculator: pick tasks and monthly volumes, see the per-call cost through Orthogonal from live catalog prices, and a field for the team's current subscriptions. Offer the result as a shareable link and a prompt for a "Book a call" for larger volumes.

    It turns the core message into a number a buyer can take to their manager, and it qualifies larger teams for the founders' calls.

    Risks and how to handle them

    • Unfair comparison with providers' plans

      Let users enter their own subscription costs instead of quoting rivals' prices.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): H1 "Get your agent the data it needs."; "Access data and services through one connection. Pay for the calls you make, without a separate subscription to each provider."; "87 APIs" and "1,774 endpoints"; "Explore all 14 categories"; per-call prices from "$0.002" to "from $0.50"; CTAs "Explore APIs", "Connect an agent", "Get your API key" and "Book a call"; no testimonials, customer logos or customer results on the page.Source
    • Your websiteSeed announcement (June 25, 2026): $4.3 million led by Pantera Capital, with Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound and Surreal by Premise; "already live in production" with GTM teams and AI-native startups; more than 35 APIs at the time, including Apollo, People Data Labs and Coresignal; fiat, x402 and MPP payment rails; the money funds "expansion of Orthogonal's engineering and go-to-market teams".Source
    • Your websiteApollo listing: "Verified", "9 endpoints" priced $0.0020 to $0.0500 per call, a "skill.md (for agents)" link, SDK and CLI quickstart, "More in Company Search" related APIs and a "Get your key" button; no call counts, latency, uptime, reviews or comparison with buying from the provider directly. The sitemap lists 85 publisher pages like it.Source
  • 16

    The catalog grew from 35+ APIs in June to 87 now, and the sitemap was updated on November 9, but there is no changelog and no newsletter signup. Users who connected months ago don't know that the APIs they asked for may now exist.

    Medium impactLow effort First result in 1 month Growth Lead

    First action

    List the APIs added since September.

    How to measure it

    Reactivated accounts

    Now
    –
    Target
    10% of dormant accounts
    By
    1 quarter

    Steps

    1. 1

      Changelog feed

      Generated from catalog changes.

      Senior Software Engineer 3 days

    2. 2

      Page

      /changelog with RSS.

      Design Engineer 2 days

    3. 3

      Signup

      Opt-in on dashboard and blog.

      Growth Lead 1 day

    4. 4

      Weekly email

      New APIs with a try-it prompt.

      Growth Lead weekly

    5. 5

      Agent feed

      Link from llms.txt.

      Senior Software Engineer 1 hour

    6. 6

      Measure

      Opens, first calls to new APIs.

      Growth Lead monthly

    First result
    1 month
    Cost
    Email tool cost
    Owner
    Growth Lead

    Smallest test

    Send one email about the last month's new APIs.

    Why it works

    Publish a changelog page generated from catalog changes (new APIs, new endpoints, price drops) and send a short weekly email to users with a one-line prompt to try each new API. Let agents read the same feed.

    For a catalog, new supply is the main reason to come back. A weekly note re-activates dormant keys at almost no cost.

    Risks and how to handle them

    • Thin weeks

      Send every two weeks when fewer than three changes.

    Evidence

    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
    • Your websiteSeed announcement (June 25, 2026): $4.3 million led by Pantera Capital, with Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound and Surreal by Premise; "already live in production" with GTM teams and AI-native startups; more than 35 APIs at the time, including Apollo, People Data Labs and Coresignal; fiat, x402 and MPP payment rails; the money funds "expansion of Orthogonal's engineering and go-to-market teams".Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
  • 17

    Orthogonal already supports organisations: members sign in to the organisation's MCP endpoint, organisation keys bill the organisation, and caps and allowed-API lists apply per key. None of this is presented as an offer, and top-ups carry a 5% processing fee. The first production customers are GTM teams, which buy as teams.

    High impactMedium effort First result in 1 quarter Founder/CEO

    First action

    List the organisations with three or more members today.

    How to measure it

    Team prepaid revenue

    Now
    –
    Target
    30% of top-ups
    By
    2 quarters

    Steps

    1. 1

      Find teams

      Organisations with several members.

      Growth Lead 1 day

    2. 2

      Interview five

      What they need to commit more.

      Founder/CEO 2 weeks

    3. 3

      Define the offer

      Commitment tiers and invoicing.

      Founder/CEO 1 week

    4. 4

      Usage by member

      Dashboard view.

      Senior Software Engineer 2 weeks

    5. 5

      Teams page

      Controls, invoicing, contact.

      Design Engineer 1 week

    6. 6

      Sell

      Founder-led to the first ten teams.

      Founder/CEO 1 quarter

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Founder/CEO

    Smallest test

    Offer invoiced prepaid balances to three teams.

    Why it works

    Create a Teams page: shared balance, per-member keys with their own caps and allowed APIs, monthly invoicing for larger balances (which can also avoid card processing fees), usage by member, and a named contact. Price it on prepaid commitment rather than a seat fee, to keep the no-subscription promise.

    Team buyers spend more and churn less than individuals, and the controls they need already exist. Packaging turns features into a reason to commit a larger prepaid balance.

    Risks and how to handle them

    • Looks like a subscription

      Keep it prepaid usage with no seat fees.

    Builds on

    Evidence

    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
    • Your websiteSpend limits docs: a daily cap per account or organisation and one per API key, counted since midnight UTC; per-key allowed-API lists ("A call to an API outside either list is refused with HTTP 403"); refusal codes DAILY_ACCOUNT_LIMIT_EXCEEDED and DAILY_KEY_LIMIT_EXCEEDED; no alerts before a cap or a low balance is reached are described.Source
    • Your websitellms.txt (checked November 10, 2026): indexes 59 per-API skill files against 87 APIs in the catalog (TinyFish, featured in a September 23 partner post, is not in it); it points providers to "List your API: https://www.orthogonal.com/docs/list-your-api", which returned 404 Not Found on two checks that day; it mentions a one-time $1 starter credit and that "Top-up packages carry a 5% processing fee".Source
    • Your websiteSeed announcement (June 25, 2026): $4.3 million led by Pantera Capital, with Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound and Surreal by Premise; "already live in production" with GTM teams and AI-native startups; more than 35 APIs at the time, including Apollo, People Data Labs and Coresignal; fiat, x402 and MPP payment rails; the money funds "expansion of Orthogonal's engineering and go-to-market teams".Source

Big bets 3

Larger plays that can change the trajectory.

  • 18

    Orthogonal started with go-to-market APIs and says it is expanding. Today GTM categories are deep (Company Data, People Data, Email Finder) while others are a single API (Weather 1, Video 1, Identity Verification 1), and all five docs use cases are GTM. A buyer outside sales tooling sees a thin catalog.

    High impactHigh effort First result in 2 quarters Founder/CEO

    First action

    Rank candidate verticals by call growth and search demand.

    How to measure it

    Non-GTM call share

    Now
    –
    Target
    25%
    By
    2 quarters

    Steps

    1. 1

      Rank verticals

      Call growth and search demand.

      Growth Lead 1 week

    2. 2

      Recruit providers

      Five to eight for the chosen vertical.

      Founder/CEO 6 weeks

    3. 3

      Onboard

      Through the onboarding agent and review.

      Co-founder & CTO 4 weeks

    4. 4

      Recipes

      Three vertical recipes with costs.

      Growth Lead 3 weeks

    5. 5

      Launch

      Joint launch with providers.

      Growth Lead 1 week

    6. 6

      Review

      New buyers and retention after 90 days.

      Founder/CEO 1 quarter

    First result
    2 quarters
    Cost
    Founder time and launch budget
    Owner
    Founder/CEO

    Smallest test

    Add three providers in one vertical and publish one recipe.

    Why it works

    Pick one adjacent vertical where agents already need paid data, for example financial and market data (Financial Datasets is already listed) or web automation (TinyFish, Olostep, scraping APIs), and make it complete: five to eight providers, recipes, a category landing page and a launch with those providers. Measure whether it brings a new kind of buyer.

    Depth in one new vertical beats one API in many. It widens the market for the next round and tests whether the model works outside GTM.

    Risks and how to handle them

    • Distracts from the GTM core

      One vertical at a time, with a go/no-go review.

    Builds on

    Evidence

    • Hacker NewsShow HN (September 1, 2026, 12 points, no comments): "one integration to discover, access, and pay for APIs" with 50+ providers and 700+ endpoints; it started with go-to-market APIs and is expanding; "The problem we're working on now is API selection", choosing providers by price, latency, reliability and result quality; the founders ask whether people would trust an agent with a budget to choose its own API provider.Source
    • Your websiteCatalog (checked November 10, 2026): "87 APIs · 1,774 endpoints"; categories AI Search (9), Brand Data (2), Browser Automation (2), Company Data (6), Email Finder (4), Identity Verification (1), People Data (6), Video (1), Weather (1), Web Data (8), Scrape (3), Search (2), LLM (2), Image (2) and Uncategorized (62); the only sort is "Most called"; cards show "Verified publisher" and "Reliable" badges and a from-price, but no call volume, latency, uptime, ratings or reviews.Source
    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
  • 19

    The founders ask in public whether people would trust an agent with a budget to choose its own API provider, and name API selection as the current problem. Orthogonal already has the pieces: many providers per task, per-call prices in every response, per-key caps and allowed-API lists. What is missing is a "do this task" call that picks the provider.

    High impactHigh effort First result in 1 quarter Co founder & CTO

    First action

    Build find_work_email over the Email Finder providers as a beta.

    How to measure it

    Task-endpoint share of calls

    Now
    –
    Target
    20%
    By
    3 quarters

    Steps

    1. 1

      Pick the first task

      A deep category with comparable outputs.

      Co-founder & CTO 1 week

    2. 2

      Normalise outputs

      One schema across providers.

      Senior Software Engineer 3 weeks

    3. 3

      Selection policy

      Cheapest, fastest or most reliable, within a budget.

      Co-founder & CTO 3 weeks

    4. 4

      Fallback

      Retry with the next provider on failure.

      Senior Software Engineer 2 weeks

    5. 5

      Explain choices

      Which provider answered and why, in each response.

      Senior Software Engineer 1 week

    6. 6

      Beta with customers

      Five production teams.

      Founder/CEO 1 month

    7. 7

      Expand

      Next three tasks.

      Co-founder & CTO 1 quarter

    First result
    1 quarter
    Cost
    Most of an engineer for two quarters
    Owner
    Co founder & CTO

    Smallest test

    One task endpoint over two providers with fallback.

    Why it works

    Offer task-level endpoints (for example find_work_email, search_web, enrich_company) that choose among allowed providers by a stated policy (cheapest, fastest, best success rate) within a per-call budget, fall back on failure, and report which provider answered and why. Start with one task in a deep category.

    It turns Orthogonal from a catalog into the layer that makes the decision, which is far harder for rivals or single providers to copy, and fallback raises success rates for every customer.

    Risks and how to handle them

    • Providers lose volume to cheaper rivals

      Publish the policy and let quality, not only price, win.

    • Outputs differ in quality

      Start where outputs are easy to compare, such as verified emails.

    Builds on

    Evidence

    • Hacker NewsShow HN (September 1, 2026, 12 points, no comments): "one integration to discover, access, and pay for APIs" with 50+ providers and 700+ endpoints; it started with go-to-market APIs and is expanding; "The problem we're working on now is API selection", choosing providers by price, latency, reliability and result quality; the founders ask whether people would trust an agent with a budget to choose its own API provider.Source
    • Your websiteSpend limits docs: a daily cap per account or organisation and one per API key, counted since midnight UTC; per-key allowed-API lists ("A call to an API outside either list is refused with HTTP 403"); refusal codes DAILY_ACCOUNT_LIMIT_EXCEEDED and DAILY_KEY_LIMIT_EXCEEDED; no alerts before a cap or a low balance is reached are described.Source
    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
    • Your websiteBreaknine case study (August 4, 2026): a tool that turns venture investors' CRM data into outreach moved its news discovery onto Orthogonal, using Fiber AI, Apollo, Serper, Bytemine, Company Enrich, PredictLeads, Fundable and Aviato; in its first two weeks it surfaced 622 updates from 233 source domains, and 539 of 622 (about 87%) were independently grounded, against "close to zero" before.Source
  • 20

    Orthogonal connects through one MCP server URL that works with any MCP client, a CLI and a TypeScript SDK. Builders, though, start in agent frameworks, templates and tool directories, and rivals such as Composio (1,700+ apps) and Smithery (thousands of tools) are already the default answer there for "give my agent tools".

    High impactHigh effort First result in 1 quarter Founder/CEO

    First action

    List the five frameworks and directories most used by current customers.

    How to measure it

    Integration-sourced signups

    Now
    –
    Target
    30% of signups
    By
    3 quarters

    Steps

    1. 1

      Survey customers

      Which frameworks and clients they use.

      Growth Lead 1 week

    2. 2

      Directory listings

      MCP directories with full descriptions.

      Growth Lead 1 week

    3. 3

      First integration

      The most used framework.

      Senior Software Engineer 1 month

    4. 4

      Templates

      Starter projects with credit.

      Senior Software Engineer 1 month

    5. 5

      Co-launch

      With framework maintainers.

      Founder/CEO ongoing

    6. 6

      Measure

      Signups and retention by source.

      Growth Lead monthly

    First result
    1 quarter
    Cost
    An engineer for a quarter plus credits
    Owner
    Founder/CEO

    Smallest test

    List in two MCP directories and track signups for a month.

    Why it works

    Become the default paid-data option in those starting points: official integrations or plugins for the most used agent frameworks, listings in MCP directories, starter templates that include an Orthogonal key with credit, and a Python SDK if call logs show demand. Co-launch each integration with the framework's maintainers.

    Distribution at the point of setup compounds: every new project created from a template starts with Orthogonal connected. It positions Orthogonal as the paid-data layer next to, not against, app-connector tools.

    Risks and how to handle them

    • Maintaining many integrations

      Generate them from the OpenAPI spec and keep to the top three.

    Evidence

    • Your websiteDocs: one MCP server URL that works with any MCP client, a one-line setup command, a CLI ("orth"), a TypeScript SDK and a REST API; guides for MCP, CLI, authentication, payments, spend limits and examples.Source
    • Competitor researchRivals' homepages: Composio, "Give your AI secure access to 1,700+ apps in minutes", with a free Hobby plan of 100,000 tool calls a month and some tools billed per call; Smithery, "Connect agents to thousands of tools and services. Auth, credentials, and sessions handled for you."; OpenRouter, the model gateway Orthogonal's founders compare it to, publishes public rankings of usage by tokens processed.Source
    • HiringSenior Software Engineer: "one of the first engineers", full stack on Vercel with a TypeScript backend, a Next.js frontend and Postgres, payments or crypto experience a bonus. Design Engineer: builds the React/TypeScript design system and component library with care for typography, motion and accessibility, and keeps the front end fast.Source

Wildcards 2

Unexpected experiments, each with a cheap way to test it.

  • 21

    Real visitors still pass Core Web Vitals (LCP 2.0 s, INP 97 ms, CLS 0.01 at the 75th percentile), so this is not a problem today. But LCP is trending 16% slower, and Orthogonal is hiring a Design Engineer to build a new design system with motion. Catalog pages will grow with stats and comparisons. Without a budget, the next redesign is where a passing site starts failing.

    Medium impactLow effort First result in 1 month Design Engineer

    First action

    Record current field data for the homepage and catalog as the baseline.

    How to measure it

    Field LCP

    Now
    –
    Target
    Under 2.0 s
    By
    1 quarter

    Steps

    1. 1

      Baseline

      Field and lab numbers for key pages.

      Design Engineer 1 day

    2. 2

      Set budgets

      LCP, JS and image weight.

      Design Engineer 1 day

    3. 3

      CI check

      Fail pull requests that exceed budget.

      Senior Software Engineer 3 days

    4. 4

      Find the regression

      What made LCP slower.

      Design Engineer 3 days

    5. 5

      Reduced motion

      Respect user settings.

      Design Engineer 1 day

    6. 6

      Review

      Field data monthly.

      Design Engineer monthly

    First result
    1 month
    Cost
    A week of engineering
    Owner
    Design Engineer

    Smallest test

    Add a Lighthouse check to one pull request pipeline.

    Why it works

    Set budgets for LCP (under 2.5 s at p75), JavaScript per page and image weight on the homepage, catalog and provider pages; add a performance check to pull requests; and review field data monthly. Make motion respect reduced-motion settings.

    Developers judge developer tools by how fast they feel, and a budget is far cheaper before a redesign than after.

    Risks and how to handle them

    • Budgets slow shipping

      Warn first, block only on large regressions.

    Evidence

    • Site researchChrome UX Report field data for orthogonal.com (real visitors, 75th percentile): LCP 2.0 s, INP 97 ms, CLS 0.01, so the site passes Core Web Vitals, but LCP is trending 16% slower; the site runs Next.js on Vercel, with Chatwoot live chat and Cal.com booking.Source
    • HiringSenior Software Engineer: "one of the first engineers", full stack on Vercel with a TypeScript backend, a Next.js frontend and Postgres, payments or crypto experience a bonus. Design Engineer: builds the React/TypeScript design system and component library with care for typography, motion and accessibility, and keeps the front end fast.Source
  • 22

    Orthogonal's buyers are builders who share prompts, agent setups and code publicly. Each call already reports its price, and recipes (idea 10) can carry a tracked link. There is no referral programme on the site, and the only growth incentive is a free-credit call to action at the end of partner posts.

    Medium impactMedium effort First result in 1 quarter Growth Lead

    First action

    Invite ten active users to publish one recipe each.

    How to measure it

    Referred paying users

    Now
    –
    Target
    50 a quarter
    By
    2 quarters

    Steps

    1. 1

      Design the reward

      Credits for both sides on first top-up.

      Founder/CEO 2 days

    2. 2

      Build tracked links

      Per user and recipe.

      Senior Software Engineer 1 week

    3. 3

      Gallery

      Public recipe pages.

      Design Engineer 2 weeks

    4. 4

      Seed it

      Ten recipes from active users.

      Growth Lead 1 month

    5. 5

      Feature

      Monthly best recipes on X and LinkedIn.

      Growth Lead monthly

    6. 6

      Guard

      Limit self-referrals.

      Senior Software Engineer 1 week

    First result
    1 quarter
    Cost
    Credits paid only on top-ups
    Owner
    Growth Lead

    Smallest test

    Give five users referral links and a credit offer.

    Why it works

    Let any user publish a recipe (prompt, APIs used, cost per run) on a public gallery with their tracked link. When a new user signs up through it and tops up, both get credits. Feature the best recipes monthly.

    Shared recipes are useful content and a referral at once, and paying in credits keeps the cost tied to real usage.

    Risks and how to handle them

    • Credit abuse

      Pay only after a real top-up, one reward per phone number.

    Builds on

    Evidence

    • Your websiteBlog and use cases: 59 posts, the recent ones mostly partner spotlights (TinyFish on September 23, 2026, then Extruct, Akta, Financial Datasets, FullEnrich) with TypeScript, x402 and MPP code and a "Try It Today" free-credit call to action; Breaknine is the only customer case study among recent posts. The docs list five use cases, all go-to-market: lead research, competitor brand and pricing research, people search, account-based research and news monitoring.Source
    • Your websitePricing docs: "You pay only for what you use. No subscriptions."; illustrative tiers Basic $0.001 to $0.01, Standard $0.01 to $0.10, Premium $0.10 to $1.00; each response returns "priceCents"; organisation API keys bill the organisation; an agent's own account "gets a one-time $1 starter credit (one per phone number)"; wallet payments over x402, MPP or Nanopayments. The page states no platform fee and does not say whether a failed call is charged.Source
    • Your websiteSitemap (263 URLs, checked November 10, 2026): 85 /publisher pages, 85 /discover/<slug>/skill.md files, 59 blog posts and 18 docs pages; no /catalog/<category> pages; no /compare, /vs or /customers pages and no top-level use-case pages (only /docs/use-cases); the site has no changelog and no newsletter signup.Source
More example playbooks and reviews
ProgrammableDigital

Show Orthogonal’s product working

Turn screenshots or the website into an animated product demo in its own brand, for the homepage, launch posts and outreach in this playbook.

Make a demo (opens programmable.digital in a new tab)

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • Primer growth strategyA performance creative and paid media agency: paid social and search management, ad creative, creative strategy, landing pages and CRO, a…23 growth ideas
  • Everlane growth strategyA US apparel brand selling premium essentials (denim, cashmere, tees, outerwear, shoes) under the "clean luxury" banner, made at partner…22 growth ideas
  • Integral Molecular growth strategyA Philadelphia biotech, founded in 2001, that discovers and characterises antibodies against membrane proteins: the Membrane Proteome…21 growth ideas
  • Phoenix growth strategyA Canadian online health clinic for men (erectile dysfunction, hair loss, weight loss, testosterone, skin care, early climax and smoking…20 growth ideas
  • Maven AGI growth strategyAn enterprise platform for AI agents that resolve customer service conversations on chat, email and voice, connecting to helpdesks, CRMs…21 growth ideas
  • Pigment growth strategyAn AI-powered business planning and performance management platform: modeling, forecasting, scenario planning and reporting for finance…22 growth ideas
  • Marvin Behavioral Health growth strategyConfidential teletherapy, psychiatry, role-specific AI coaching, workshops, crisis and leave support built only for healthcare workers…22 growth ideas
  • Close growth strategyA sales CRM with built-in calling, email, SMS, workflows, reporting and Chloe, an AI sales agent that calls and qualifies leads, books…20 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Orthogonal did not commission, review or endorse it, and Programmable is not affiliated with Orthogonal. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Orthogonal runs its business.

Something wrong, or do you represent Orthogonal? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    Discovery hygiene and first-dollar clarity: categorise the catalog, fix llms.txt and the provider guide, one live count, indexable category pages, homepage proof and the starter-credit menu.

  2. Days 31 to 609 ideas

    Selection and trust: listing stats, the monthly most-called index, task recipes, provider co-marketing, seller terms, spend alerts, the failed-call policy, the cost calculator and the weekly new-APIs email.

  3. Days 61 to 906 ideas

    Package teams, pick the next vertical, start budgeted provider selection and framework distribution; set a speed budget for the redesign and launch recipe referrals.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value one key and one balance instead of a subscription to each data provider. The most cited problem: integrating and maintaining each API provider separately.

  • Pay-per-call prices from a fraction of a cent
  • Choosing which provider to call for a task
  • In their words: “one connection”

Market

Competitive landscape

4 competitors compared: Composio, Smithery, OpenRouter and Providers selling direct (Apollo, Hunter, Tavily and others).

  • Gap to exploit: Public, per-API data on usage, latency and success for agent builders
  • Composio: Built around connecting the user's own apps rather than buying third-party data per call
  • Smithery: No single paid balance across data providers

Hiring signals

Orthogonal, a two-person YC W26 team with a $4.3 million seed, is hiring its first growth and product team in San Francisco.

  • Growth Lead: Revenue growth past 0-to-1, demand generation and A/B tests. Ideas 1, 5, 9, 10, 11.
  • Senior Software Engineer: One of the first engineers; payments experience a bonus. Ideas 2, 3, 13, 19.
  • Design Engineer: A new design system with motion and a fast front end. Ideas 8, 21.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks first (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence