Skip to main content
Juiced has a handful of core nouns that show up everywhere. Once these click, the rest of the documentation reads a lot faster.

​
The supply side

Sources

The API endpoints where leads arrive. Each source belongs to a lead category and has its own credentials.

Leads

An individual prospect submitted to your platform. A lead is evaluated, priced, and routed to a buyer.

Lead categories

The schema for a kind of lead you sell—e.g. Auto Insurance, Solar, Home Services. Defines the fields every lead in that category carries.

Lead types

Pricing tiers within a category. Conditions decide which leads qualify for which type; a fallback type catches everything else.

​
The selling side

Distribution

The pipeline a lead flows through after it arrives. Composed of stages—most tenants use Bidding and Marketplace.

Bidding

Real-time auctions where customers compete on price for matching leads. Each lead type has its own bidding rules.

Marketplace

A fallback stage where unsold leads are offered at a fixed price to any eligible customer.

Ping-post

An alternate distribution pattern where partners respond to a “ping” with a bid before receiving the full lead.

​
The people

Customers

The buyers who purchase leads from you. They fund a wallet, place bids, and receive leads.

Partners

External ping-post buyers you distribute to. Different from customers—partners sit outside the wallet model.

​
How it fits together

A lead arrives at a source → gets classified against the source’s lead category and matched to a lead type → enters distribution → runs through stages like bidding and the marketplace → the winning customer or partner receives it, and the wallet or invoice is settled. That’s the whole loop. Everything else in Juiced—budgets and caps, duplicate detection, returns, notifications, webhooks—exists to make that loop run cleanly at scale. Ready to build one? Head to the Quickstart.