API.market · Inside a working team
How API.market finds new API sellers with Yodu.
See how API.market uses Yodu to review search data, identify missing APIs, research providers, and prepare seller outreach—with tasks and approvals you can inspect.
Explore API.marketA developer is searching
The company
A marketplace for APIs and AI models.
API.market helps developers discover APIs, read their documentation, and subscribe. API providers can list and sell their products through the marketplace.
API.marketA look inside the marketplace
AeroDataBox
Aviation data for travel products and flight tracking.
Trueway Routing
Route calculations for location-aware applications.
Illustrated product selection · open a listing to explore the actual API
How the team finds and contacts potential sellers
Developers sometimes search for APIs the catalog doesn’t have.
Those searches give the team a starting point for finding new sellers. Yodu employees review the demand, check existing listings, and research providers that could fill the gap.
The operating workflow described by Shashank Agarwal, founder of both API.market and Yodu. The task examples below show specific parts of it in practice.
SEO Content → Chief of Staff
Review the SEO backlog against current search data.
SEO Content reviewed 50 imported issues against fresh Search Console data. The result was a recommendation set the Chief of Staff could inspect and accept.
API Discovery → Seller Outreach
Turn a missing API category into a provider shortlist.
API Discovery’s financial-data shortlist gave Seller Outreach a specific category to investigate. The final task record reports a researched provider, approved campaign entry and personalized copy.
There’s demand for congressional trading data. Check this provider’s API coverage and seller fit.
Provider research is ready. I’ve prepared a product-specific introduction and three follow-ups for review.
Owner review
Keep outreach waiting until it’s approved.
A separate calendar-API task was still waiting for an Instantly approval decision when we reviewed it. The research was recorded, but we couldn’t confirm new outreach had been sent.
Add researched lead to an outreach campaign
- Provider and product-fit evidence
- Personalized message and follow-ups
- Requested external action
Illustrations of the workflow, informed by API.market task records. These are not live conversations.
Connected tools
Connect the tools each employee needs.
Employees use connected tools to check search performance, research providers, and prepare campaigns. MCP supports tool connections; each employee’s access and approval settings determine what it can do.
Google Search Console
Queries, clicks and CTR inform the research brief.
API.market
Catalog discovery checks whether a product fits the demand.
Apollo + web research
Provider research establishes product fit and contact routes.
Instantly
Approved leads and personalized sequences enter the campaign.
Workflow tools described by the founder and referenced in task records. Connection methods and available actions depend on the integration.
Read the tool-access guideFrom the workspace
Check the research, drafts, and review decisions.
We reviewed these task records through Yodu MCP. Each example includes the employee’s reported result and the review that followed. Private contact details and lead identifiers are omitted.
September 5, 2026 · Review accepted50 SEO issues, checked against fresh search data.
SEO Content reconciled the imported backlog with Search Console evidence: 22 keep, 17 re-derive, 7 merge and 4 close. The Chief of Staff accepted the recommendation set. Publishing and bulk board changes remained separate actions.
September 9, 2026 · Campaign entry recordedA catalog gap becomes personalized outreach.
An API Discovery handoff led Seller Outreach to research a financial-data provider. The task records an approved Instantly lead with a personalized subject, opening message and three follow-ups, followed by a reviewer’s acceptance.
September 13, 2026 · Owner decision neededA calendar-API campaign waiting for approval.
A separate calendar-API outreach task remained blocked on an Instantly approval decision. Its discussion contains conflicting progress reports, so we do not count it as newly sent outreach.
Campaign snapshot
47.8%Durchschnittliche positive Antwortquote
Unweighted average of the positive-reply percentages shown for the first three campaign steps.
Positive replies by campaign step
The supplied campaign view reports positive-reply percentages for three stages. Averaging those stage percentages gives the figure here. It describes the mix of replies at those stages, not the share of unique prospects who replied.
How this number is calculated
(33.3% + 60% + 50%) ÷ 3 = 47.8%, rounded to one decimal. Each step receives equal weight. This summarizes the reported positive-reply percentages; it is not the overall campaign reply rate or the percentage of unique recipients who replied. Follow-ups reach overlapping recipients, and step volumes differ. The fourth step has no reported positive-reply percentage and is excluded.
API.market · Inside a working team
What would you ask your first AI employee to do?
Tell us about the job and the tools it needs. If there’s a fit, we’ll send a Calendly link so you can book a setup call with Shashank.
Sign up · 10 limited seats$499/month from the first month, including personal account and AI employee setup with Shashank. No free trial.