Files
Review generated DD artifacts and uploaded project documents in one place, without leaving the console shell.
Recent generated
24 items in the current scope.
Parsor · Screening Card
Parsor
Parsor · IC Memo
Parsor
Perplexity Ai · IC Memo
Perplexity AI
Perplexity Ai · Screening Card
Perplexity AI
Dune Polygala Ai · IC Memo
Dune (polygala-ai)
Dune Polygala Ai · Screening Card
Dune (polygala-ai)
Dune By Polygala Ai · IC Memo
Dune (by polygala-ai)
Dune By Polygala Ai · Screening Card
Dune (by polygala-ai)
Paperclip Ai Orchestration · Screening Card
Paperclip (AI Orchestration)
Paperclip Ai Orchestration · IC Memo
Paperclip (AI Orchestration)
Connectonion · Screening Card
ConnectOnion
Cursor Anysphere · Screening Card
Cursor (Anysphere)
Cursor Anysphere · IC Memo
Cursor (Anysphere)
Legora · Screening Card
Legora
Legora · Screening Card
Legora
Harvey · Screening Card
Harvey
Harvey · Screening Card
Harvey
Lovable · Screening Card
Lovable
Lovable · Screening Card
Lovable
Orthogonal · Screening Card
Orthogonal
Aiyu Intelligence · Screening Card
Aiyu Intelligence
Taku · Screening Card
Taku
Spatial Walk · Screening Card
Spatial Walk
Spatial Walk · Screening Card
Spatial Walk
Orthogonal · Screening Card
archive/dd-reports/orthogonal_screening_card.md
Type
Screening Card
Subject
Orthogonal
Updated
3月23日 08:37
Size
3.0 KB
Preview
Rendered directly from the stored file.
Deal Screening Card: Orthogonal
Date: 2026-03-23 Analyst: DD Memo Writer (AI) Stage: Seed (YC W26) Sector: AI Infrastructure / Agentic Commerce
One-Liner
Orthogonal provides a unified SDK and payments infrastructure that allows AI agents to autonomously authenticate with APIs and execute financial transactions.
Scorecard
| Dimension | Score | Signal |
|---|---|---|
| Team | 9/10 | 🟢 |
| Market | 8/10 | 🟢 |
| Competition | 4/10 | 🟡 |
| Product/Tech | 7/10 | 🟢 |
| Financials | 5/10 | 🟡 |
| Risk | 6.5/10 | 🟡 |
| Overall | 6.6/10 | 🟡 |
Scoring: 🟢 >= 7 | 🟡 4-6 | 🔴 <= 3 Risk score inverted: 🟢 <= 3 (low risk) | 🔴 >= 7 (high risk)
Key Strengths (Top 3)
- Elite Founder-Market Fit: Founders hail from Stripe, Vercel, and Coinbase (Tier S source), providing the exact intersection of payments, developer experience, and crypto-rails expertise needed for agentic commerce.
- First-Mover in "Neutral Utility" Positioning: By building a cross-platform layer (using protocols like Coinbase’s x402), Orthogonal aims to be the neutral plumbing that avoids model-provider lock-in (OpenAI/Anthropic).
- High Developer Mindshare: Ranked as "A-Tier" in early YC W26 sentiment analysis with organic traction from top-tier engineering communities (Tier B/S sources).
Key Concerns (Top 3)
- Regulatory "Know Your Agent" (KYA) Walls: Current banking/KYC frameworks require a "Natural Person." If regulators don't accept Non-Human Entities (NHE), the autonomous vision is capped by human-in-the-loop friction (Tier A risk).
- Incumbent Disintermediation: High risk that Stripe or OpenAI vertically integrates the payment/API layer. Stripe's entry into "Stripe for Agents" would directly challenge Orthogonal’s core moat.
- Liability & Security Cascades: A single "runaway agent" draining a wallet or abusing an API key could lead to severe reputational damage or a "regulatory winter" for the sector.
Verdict
Recommendation: Deeper Look Reasoning: The team pedigree and the macro shift toward agentic commerce make this a high-conviction "bet on the category." However, the structural risks regarding regulatory compliance and Stripe’s inevitable entry require a deep-dive into their specific "moat" strategy beyond just being first to market.
Questions for Founder Meeting
- The Stripe Counter-Move: How does Orthogonal win if Stripe launches a native "Agent Identity & Billing" suite next quarter?
- KYC Workarounds: What is the specific legal roadmap for handling "Non-Human Entity" payments? Are you pursuing a "Human-Bound" guarantor model or a pure crypto-rail?
- API Vendor Relations: How do you prevent API providers (Google, X, etc.) from blocking your aggregator to protect their own direct billing relationships?
- Safety Granularity: Can you demonstrate the "Spending Guard" and permissioning logic? How do you prevent prompt injection from triggering unauthorized spend?
What belongs here
Generated docs
Screening cards, memos, and other DD outputs written by the workflow.
Project uploads
Decks, PDFs, and supporting files uploaded into Korok for context.
Daily handoff
Use this tab as the review shelf before jumping back into DD.