startups.as

startups as

APIs.Supply apis.supply

namespace seednamespaceMarketplace

Vendor records, catalogs, RFQs, purchase orders and invoices as functions an agent calls, with the X12 850 and 810 translation done once underneath by transactions.dev, so a distributor's system and a buyer's agent meet on one record.

From the Startup card at api.sb/apis.supply · Designed · App, Dataset, Marketplace, Agent.

contested · 1 tension
  • tier: namespace · discovery lens A reads namespace (namespace); lens B reads discovery (view)

The two lenses (and any ledger statement) are kept side by side, not resolved. Most names carry one; it is a reading to explore, not an error.

What it is

TiernamespaceInferred · med · portfolio-lens-a.tsv (tier)
Statusnamespace seedInferred · med · lens A tier namespace
Product kindMarketplaceInferred · low · seed rule: lens B abstraction D-catalog; product kinds per studio CONTEXT.md (Cloud · Data · Software · Service · Commerce · Marketplace)
Core nounCapability listingInferred · low · seed rule: the unit noun of lens B abstraction D-catalog (portfolio-lens-b.md §1)
Buyer and positionVertical cut of the API catalog (scope: supply); promotes to a projection once a supply abstraction is builtInferred · med · portfolio-lens-b.tsv (icp_or_position)
Closed set or journeyS20 api(s).[vertical] namespace · supplyInferred · med · portfolio-lens-a.tsv (set_or_journey)
AbstractionD-catalogInferred · med · portfolio-lens-b.tsv (abstraction)
Role (lens B)discoveryInferred · med · portfolio-lens-b.tsv (role)
RegistrarporkbunInferred · high · holdings ledger (domains repo, read-only)

Its stack

  1. Generated around APIs.Supply

Click any node to re-centre the stack on it; the trail above keeps the nesting. Each node's own page is one more click.

Neighbours

Relationships (5)

fromverbtoprovenance
APIs.Supplyruns-on
logo row: "Powering" / "Built on" (customer runs on supplier)
API.SB Inferred · high · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvruns today
api.sb/apis.supply answers (status Designed, fetched 2026-10-24)
APIs.Supplylisted-by
logo row on a catalog venue (listed by)
APIs.Directory Inferred · high · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvruns today
listed on live apis.directory (fetched 2026-10-24)
APIs.Supplylisted-by
logo row on a catalog venue (listed by)
Agentic.Services Inferred · low · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvbuildable
sb def agentic.services: supplies apis.supply [low] — targets.jsonl gives it the procurement function and relates it to apis.supply; a procurement agent sourcing a back-office service would find
APIs.Supplyruns-on
logo row: "Powering" / "Built on" (customer runs on supplier)
Transactions.Dev Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified
sb def apis.supply: built on transactions.dev [medium] — The X12 documents are compiled and parsed by transactions.dev's engine (parse, validate, ack) rather than rebuilt; stated by r4-domains, and
APIs.Supplyruns-on
logo row: "Powering" / "Built on" (customer runs on supplier)
StartupBuilder.Dev Inferred · medium · docs/plans/research/2026-10-24-builder-brands/logo-graph.tsvspecified
sb/poc/startup-as-noun/defs/apis.supply/startup.data.mdx

Sign in to curate.

Edit log

loading the versions of this record from api.sb…

Machine-readable: /apis.supply.json