Loading video...

Video Failed to Load

Go Home

Introducing: OpenRouter for everything. One prepaid balance for every API your agents and products need. It’s the billing and metering layer every AI team needed from day one. An OpenRouter for everything. Every model call, search, scrape, or data request - one key, one balance, charged as it happens...

76,129 views • 1 month ago •via X (Twitter)

45 Comments

Samuel Spitz's profile picture
Samuel Spitz1 month ago

@techbyved This is cool, how did you make the video? Remotion? Looks good. You should try Replit Animation sometime.

cole's profile picture
cole1 month ago

@techbyved Actually video was made with Fable 5, took some iteration of course. I'll give it a try! Shot you a dm as well :-)

cole's profile picture
cole1 month ago

I’ve been wanting to use this track for a launch for awhile, glad I finally could :-) Also docs here:

Aman's profile picture
Aman1 month ago

this is gonna make agent billing so much simpler

cole's profile picture
cole1 month ago

Indeed!

ved luhana's profile picture
ved luhana1 month ago

Can’t wait to see adoption go up and up

cole's profile picture
cole1 month ago

Indeed, we’ll keep pushing

Alexandre Dennis priv/acc's profile picture
Alexandre Dennis priv/acc1 month ago

Agents got a budget. Now give them a mandate.

s's profile picture
s1 month ago

You'll only ever need one api endpoint again

cole's profile picture
cole1 month ago

Model routing❌ API routing✅

Kai Lennox's profile picture
Kai Lennox1 month ago

This is actually a really clean idea. One balance for the whole AI stack would save so much billing pain.

Shiyi Peng's profile picture
Shiyi Peng1 month ago

congrats!! this is so cool🚀

Raj Nagulapalle's profile picture
Raj Nagulapalle1 month ago

billing consolidation across 2,400+ endpoints is genuinely hard to pull off. failed calls costing nothing is the detail that'll matter most to agent builders running at scale.

Shreyans Bhansali's profile picture
Shreyans Bhansali1 month ago

i've built enough agent infra to hate provider billing. one key and one ledger sounds boring in exactly the right way

cole's profile picture
cole1 month ago

🫡

Nick Khami's profile picture
Nick Khami1 month ago

this product makes a ton of sense for all the vibecoding solutions out there

Sreeram Garlapati's profile picture
Sreeram Garlapati1 month ago

The interesting part isn’t consolidating API keys, it’s turning fragmented AI infrastructure into a predictable cost layer. Once teams can meter, cap, and pass through every model and data call, AI usage starts looking like a normal infrastructure expense instead of a billing nightmare.

Sebastian Buzdugan's profile picture
Sebastian Buzdugan1 month ago

one leaked key can drain every service, are spend caps enforced per agent

cole's profile picture
cole1 month ago

Yup

P's profile picture
P1 month ago

great idea

cole's profile picture
cole1 month ago

🫡

Ken Wattana's profile picture
Ken Wattana1 month ago

Great stuff!

Roger R.'s profile picture
Roger R.1 month ago

Agents are gig workers

alissa (nyc!)'s profile picture
alissa (nyc!)1 month ago

This is sick!!

P's profile picture
P1 month ago

locus team is cooking

cole's profile picture
cole1 month ago

Thank you sir!

Gsci's profile picture
Gsci1 month ago

LOCUS

prapa's profile picture
prapa1 month ago

LOCUS

armandoki's profile picture
armandoki1 month ago

@ycombinator This is smart

aaron's profile picture
aaron1 month ago

LOCUS. 🫡

Phillip Yan's profile picture
Phillip Yan1 month ago

Congrats on the launch!

Kovan's profile picture
Kovan1 month ago

super cool

Sina Matian's profile picture
Sina Matian1 month ago

There should be a feature to sell unused AI credits. For example, If i have $200 in deepseek credits, since deepseek is on locus I can sell those credits to Locus, then get $200 Locus credits or $180 cash etc.

Tykoo's profile picture
Tykoo1 month ago

LOCUS

John Wei's profile picture
John Wei1 month ago

the agent handles the mess, you just pay one bill

cole's profile picture
cole1 month ago

Exactly 🫡

Sahib Nanda's profile picture
Sahib Nanda1 month ago

@ycombinator Portfolio: GitHub: SDE @CRED. Built an AI portfolio backend with Orchestrator/Worker logic and a custom MCP tool-calling layer. I know the infra cost of running agents. DMing.

Ian Janicki's profile picture
Ian Janicki1 month ago

Congrats! @zincdotcom would love to be a provider!

Fahim Ahmed's profile picture
Fahim Ahmed1 month ago

This is awesome, congrats Cole!

cole's profile picture
cole1 month ago

Thank you thank you sir

Chloe's profile picture
Chloe1 month ago

finally, a way to stop chasing 20 different developer API keys.

Keita's profile picture
Keita1 month ago

COOL! LFG Cole & Locus team🔥

Dariya's profile picture
Dariya1 month ago

Epic

cole's profile picture
cole1 month ago

E🅿️ic

Malibu's profile picture
Malibu1 month ago

wow

Related Videos

how you can use openAI codex & gpt 5.5 completely FREE (the full guide) 100% legit. no subscription, zero API cost. up to 1M+ token/day. you need just an openAI account and here's how to set it up in 5mins. openAI has a program that gives eligible developers free API usage every day in exchange for sharing API data that helps improve future models. it's not a one-time credit, your allowance refreshes daily. depending on your usage tier, you can get access to hundreds of thousands, or even millions, of free tokens every single day on supported models. here's how to activate it: 1️⃣open your API dashboard: 2️⃣go to settings → data controls 3️⃣enable data sharing for your organization or project 4️⃣make sure your account has a positive API balance 5️⃣save the settings if your account is eligible, you'll see a message confirming access to complimentary daily usage. before you turn it on, know the tradeoff: • prompts and outputs from shared projects can be used to improve openai's models • don't use it for confidential information, client work, or sensitive data • eligibility depends on your account type and settings for everyone else, it's an incredible deal. use it to: • learn AI development • build side projects • experiment with codex • test agents and automations • prototype ideas without worrying about API costs most developers burn money testing ideas. this lets you experiment at scale while spending little to nothing.

m0h

71,147 views • 4 months ago

.OpenRouter co-founder Alex Atallah, in his first podcast since Stripe acquired the company, joins Replit ⠕ co-founder Amjad Masad and a16z's Erik Torenberg on why the future of AI is independence and specialization. In this conversation, Alex walks through how the Stripe deal unfolded, why he wasn't originally looking to sell, and why "payments and inference are going to blend together." Pre-OpenRouter, the typical AI workflow had one model provider to choose from, and little pressure on that provider to lower prices. Now enterprises are diversifying across labs and open-weight models, and every board is asking about AI costs and benchmarks. Amjad argues if your company depends on one AI lab, it can turn into your competitor. So Replit is building the layer that lets enterprises use any model and any cloud, without being locked into either. Alex and Amjad are split on personal agents – Amjad runs one agent across his whole company and loves the cross-domain joins, while Alex says general agents cause you to sacrifice understanding, and argues 10 specialized chiefs of staff beats one superagent. 0:45 How the Stripe deal unfolded 5:05 Why mixing models beats one model 7:25 Forcing the labs to compete on price 8:50 Enterprises want open-weight models 10:30 Every board asks about AI every month 12:25 Why companies must own their intelligence 14:15 Replit as the independence layer 15:10 Everyone is building the same agent 16:35 Why Amjad built bring-your-own-cloud 18:10 Amjad's agent that runs his whole company 19:55 Why 10 specialized agents beat one 23:35 Machines, not humans, should specialize 27:30 Guardrails for agents talking to agents 31:10 Models training their own replacements 33:45 Most tasks don't need a frontier model 40:50 Training small models on Qwen 8B 43:25 The Rust cycle is coming for AI 45:10 Fusion models: frontier quality at half the cost YouTube: Alex Atallah OpenRouter Amjad Masad Erik Torenberg

a16z

551,070 views • 9 days ago

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

20,121 views • 1 month ago