jimmy·research
Home/Agentic Commerce/Locus
EN↔中文
Company

Locus

Payment infrastructure + paid-API aggregator for AI agents — wraps 32+ third-party APIs as MPP-compatible endpoints on tempo-mpp with policy-driven spending controls.

1. Core Product / Service

Locus self-positions as "the control layer + API aggregator/distributor for agentic payments", with two product lines growing together:

  • Payment control layer: assigns agents identity / budget / per-tx limits / audit logs; the underlying rail is USDC on Base, with roadmap including ACH and wire (2026-05-09 official site). Example policy: "max $50/tx, $500/day, only category=API".
  • API endpoint catalog: 32+ pay-per-use APIs (Perplexity, Brave, Tavily, SerpAPI, Apollo, Finnhub, CoinGecko, DeepL, etc.) uniformly wrapped as tempo-mpp-compatible https://*.mpp.paywithlocus.com/... endpoints; one agent call auto-settles (measured in raw notes 2026-04-02).
  • Pricing mechanism: 2-3x markup on top of the underlying API vendor cost. Measured sample: Perplexity Sonar chat API at ~$0.005 native, Locus charges $0.015 via Tempo; Perplexity /search ~$0.007/call (raw 2026-04-02-diary-claudecode.md).

2. Target Users & Pain Points

  • Target users: agent developers running on tempo-mpp, engineering teams that need to quickly integrate multiple paid APIs but don't want to sign contracts / manage keys / handle micropayments one by one.
  • Core pain points:
    1. Traditional agent use of paid APIs requires per-vendor account registration, card binding, key management, and reconciliation — not autonomous-agent friendly.
    2. Tempo's native MPP service coverage is narrow (~20), missing finance data / search enrichment / sales data and other long-tail.
    3. Corporate finance wants to set hard limits and auditing on the agent, but raw credentials like OpenAI key, Stripe key have no native policy layer.

Locus uses one wrapper + one contract + one wallet to solve three things: catalog, payment, and policy.

3. Competitive Landscape

Player Positioning Difference vs Locus
tempo-mpp native services Direct Stripe+Paradigm micropayment channel Tempo's ~20 directly-connected native services (*.mpp.tempo.xyz) have low markup but narrow catalog; Locus sits on the outer ring doing long-tail distribution
eden-ai Multi-model / multi-API aggregator (traditional SaaS billing) Eden AI is subscription / postpaid, targets human developers; Locus uses stablecoin per-call, targets agents
portkey-ai LLM gateway + routing + observability, plus budget controls Portkey is strong at LLM-only routing / observability; Locus is strong at cross-category API aggregation + true on-chain settlement
openrouter LLM API router, unified billing OpenRouter only covers LLMs; Locus covers non-LLM APIs like search / finance / sales data
Direct calls to native APIs Self-managed keys / self-managed billing No agent-friendly policy layer and audit trail

Locus's differentiation = "the only middleman within the Tempo ecosystem to batch long-tail APIs into the MPP protocol and stack a policy layer on top".

4. Unique Observations

  • Essentially an arbitrage middleman: on APIs Tempo hasn't natively integrated, Locus uses wrapper + markup to capture a 50%-200% price gap. Short-term high growth, long-term squeezed by Tempo native integrations (raw 2026-04-02). Once Tempo directly connects Perplexity / Brave, Locus's existence on that API is zeroed out.
  • The real moat may not be in the API catalog but in the policy/audit layer: pure catalog / pricing layer can be replicated by anyone; if Locus turns "agent identity + spending policy + cross-rail audit" into a SOC2-grade compliance product, it could decouple from Tempo and stand alone (see agent-payment-protocols for the policy-layer gap).
  • Larger footprint than the GTM description suggests: Tempo users have a high probability of actually hitting Locus — when Jimmy was debugging OpenClaw connecting to Tempo Perplexity, the default path was perplexity.mpp.paywithlocus.com rather than Tempo native (raw 2026-04-04). This means Locus is de facto Tempo's default distributor, positioning itself through speed of breadth.
  • YC batch correction: internal early notes recorded W25, but the official YC page (2026-05-09) and LinkedIn company verification both show F25 (Fall 2025). Correct batch is F25.
  • 2-person team + Beta phase: as of 2026-05-09 still a 2-person team; the company runs largely on wrapper standardization (one SDK connecting N APIs).

5. Financials / Funding

  • YC F25 standard amount: ~$500K @ 7% (YC standard SAFE, implied valuation cap ~$1.78M), no rounds disclosed beyond this in public channels (YC official site + Tracxn, 2026-05-09).
  • Third-party database startuphub.ai lists "$8M Raised" (2026-05-09) — but the aggregator gives no investor or round breakdown, and there's suspected data confusion with same-named older companies "Locus Robotics / Locus Technologies"; not treated as a credible source for now, pending YC Demo Day / TechCrunch / Crunchbase confirmation.
  • Revenue model: markup take (2-3x) per API call, settled in USDC on the Tempo chain. Revenue scale not disclosed; given Tempo TVL is only ~$31K early on (raw 2026-04-02), actual GMV is estimated in the monthly 4-5 digit USD range.

6. People & Companies

  • Founders:
    • Cole Dermott — CEO / co-founder, former coinbase-agentkit parent Coinbase B2B payments intern (summer 2025); LinkedIn shows concurrent "Locus (YC F25)".
    • Eliot Lee — co-founder, formerly Scale AI data pipeline (serving top AI labs).
  • Investors:
    • Y Combinator (F25 batch) — only publicly disclosed investor, standard deal.
    • Other angels / pre-seed not yet disclosed.
  • Partners / upstream:
    • tempo-mpp — sole payment channel host; Locus exists entirely dependent on the Tempo MPP protocol.
    • Upstream API suppliers: Perplexity, Brave, SerpAPI, Tavily (same as tavily-search-integration), Finnhub, Apollo, CoinGecko, DeepL, and 32+ others.
  • Competition / adjacency:
    • eden-ai — traditional multi-API aggregator, subscription model.
    • portkey-ai — LLM gateway + budget control, overlapping policy layer.
    • openrouter — LLM API routing, minimal overlap (LLM category only).
    • surf — crypto data adjacent service (also runs paid API + agent skill mode).

Sources

Related

tempo-mppeden-aiportkey-aisurfopenrouter
Last compiled: 2026-05-09