# Orthogonal

> Canonical: https://www.yalc.ai/tools/orthogonal/

Trusted skills and APIs. The building blocks your agent needs.

## Categories

- intelligence
- prospecting

**Website:** https://www.orthogonal.com/?utm_source=yalc&utm_medium=referral&utm_campaign=in-app

## Glance

- Pricing: Custom
- Backed by: Y Combinator
- Label: Works with
  - Value: Claude Code

## Pricing

**Starting Usd:** 0

**Summary:** Custom pricing

### Narrative

Orthogonal pricing is not public on the homepage. The product is positioned as infrastructure for AI agents, with 40 plus partner integrations and skills available across Claude Code, Cursor, OpenClaw, and Codex. Pricing is likely per skill consumption or per agent seat. Talk to the team for current rates.

The interesting angle for Yalc is that Orthogonal and Yalc share the same surface (Claude Code) and overlap in some skill primitives. Orthogonal provides composable capability bricks. Yalc provides the GTM operating system that orchestrates them.

### Tiers

- **Free / waitlist**
  - Price: $0
  - Note: Some skills available to evaluate. Sign up for early access.
- **Team**
  - Price: Custom
  - Note: Pricing scaled to skill consumption and seats. Talk to sales.
- **Enterprise**
  - Price: Custom
  - Note: Dedicated infra, SLA, custom skill development. For large GTM teams.


**Yalc Fit Score:** 7

**Yalc Verdict:** Useful as a skill marketplace for capabilities Yalc doesn't ship natively. Treat it as supplementary infrastructure, not a replacement for Yalc's own GTM specific skills.

## Plain Description

Orthogonal is positioning itself as a layer of "trusted skills and APIs" for AI agents. The product surface is intentionally minimal in public messaging: building blocks, integrations, agent compatibility. The 40 plus partner integrations span scraping (ScrapeGraph), prospecting, and other categories.

For Yalc workflows, Orthogonal is a complementary skill source. Where Yalc ships skills purpose built for GTM (Crustdata MCP, Unipile outreach, Notion CRM), Orthogonal can supply general purpose infrastructure (web scraping primitives, document parsing, niche API wrappers) that Yalc doesn't need to build in house.

## Yalc Framework

**Workflow Step:** intake

**Workflow Narrative:** Orthogonal sits at the **intake** node when you need a capability Yalc doesn't ship natively (specialized scraping, document parsing, a vendor not in the Yalc skill registry). Most Yalc workflows won't touch Orthogonal directly. The ones that do treat it as a fallback source for niche capabilities.

**Workflow Position:** Supplementary skill source. Yalc invokes an Orthogonal skill when none of its native skills (Crustdata, Unipile, FullEnrich, Firecrawl) cover the specific capability needed. The output flows back into the standard Yalc pipeline.

### Prompt Patterns

- Yalc, use the Orthogonal ScrapeGraph skill to extract structured data from these 50 vendor pricing pages. Output a normalized table with name, price, billing cycle, and feature list.
→ Yalc invokes Orthogonal's wrapper around ScrapeGraph, normalizes the output.

- Yalc, when the GTM agent decides it needs a capability not in our native skill set, search the Orthogonal registry first before writing custom code.
→ Yalc treats Orthogonal as the "before custom" fallback layer.


### Chaining

**Upstream:** Yalc prompt → Orthogonal skill (intake or specialized capability)

**Downstream:** Orthogonal output → standard Yalc pipeline (Notion, Crustdata, Unipile)


### Anti Patterns

- Don't use Orthogonal for capabilities Yalc already ships natively. The Crustdata MCP, Unipile skill, and FullEnrich integration are deeper than equivalent Orthogonal wrappers.
- Don't build a Yalc workflow that depends on a single Orthogonal skill without a fallback. Skill availability and pricing can change.
- Don't conflate Orthogonal and Yalc in user facing messaging. Orthogonal is a skill source. Yalc is the GTM operating system that orchestrates skills.

**Skill Narrative:** No first party Yalc skill wraps Orthogonal directly. Yalc invokes Orthogonal skills via the same Claude Code skill protocol Orthogonal uses publicly. Integration is by convention, not by custom code.


## Pros

- 40 plus integrations available out of the box
- Works inside Claude Code, Cursor, OpenClaw, Codex (multi agent surface)
- Y Combinator backed, active product, fast iteration
- Useful for capabilities outside Yalc's GTM core (general scraping, document parsing)

## Cons

- Public docs are sparse. You'll need to talk to the team to understand the surface.
- Pricing not public. Procurement friction for solo operators.
- Overlaps with Yalc's native skills in some areas. Decide which is canonical for your workflows.
- Less GTM specific than Yalc itself.

## Who For

- GTM teams who already use Yalc or another orchestration layer and need supplementary skill primitives
- Engineers building agent workflows who want a skill marketplace alongside custom code
- Operators who want to pilot agent infrastructure without committing to a single vendor

## Alternatives

- **Native Yalc skills**
  - Rule: Use these first for GTM specific capabilities (prospecting, outreach, CRM, content).
  - Url: #
- **Custom Claude Code skills**
  - Rule: Switch when the capability is unique to your workflow and not worth a third party dependency.
  - Url: #
- **Composio / Pica**
  - Rule: Switch when you want a different vendor in the same skill marketplace category.
  - Url: #

## Faq

- Q: Is Orthogonal a competitor to Yalc?
  - A: They overlap on surface (Claude Code) but solve different problems. Yalc is a GTM operating system with opinionated workflows for prospecting, outreach, content, and intelligence. Orthogonal is a skill marketplace for general purpose agent capabilities. They compose rather than compete.
- Q: When should I use Orthogonal instead of writing a Yalc skill?
  - A: When the capability is generic (scraping, document parsing, niche API wrapping) and not GTM specific. For prospecting, enrichment, outreach, CRM writeback, Yalc's native skills are deeper.
- Q: How much does Orthogonal cost?
  - A: Not public. Pricing scales with skill consumption and seats. Best to talk to the team.
- Q: Does Orthogonal work with Claude Code?
  - A: Yes. The product explicitly supports Claude Code, Cursor, OpenClaw, and Codex.
- Q: Can I use Orthogonal without Yalc?
  - A: Yes. Orthogonal is independent infrastructure. Yalc is one of many possible orchestration layers on top.
- Q: Is there a free tier?
  - A: Some skills are available to evaluate. Full pricing requires a sales conversation.

**Reviewer:** Othmane Khadri