Three steps. No install.
See your first estimate
Watch the replay above — it's the real mechanism, not a mockup. The install command ships to early access first, credit already tracking.
Your first run pays out
Your agent provisions like normal — Concierge matches the request in ~200ms and a credit lands for the pick that won.
Keep it — and earn
Add one line to AGENTS.md and every provision routes through Concierge. A share of each accrues; sign in only to cash out.
Adopt the open standard
Ship the Skill and an AGENTS.md line across your user base — or wire the MCP for deeper control. One neutral integration, no UX changes, no provider contracts to sign.
Agent traffic becomes an auction
Every provisioning call your users make clears a bid at the exact moment of intent.
You keep 70–80%
A per-session revenue line from traffic you already have — without raising prices or adding ads.
Start with the program you already run
Route through your existing affiliate program on day one — no new integration, no BD. Add your LTV data and the auction bids on your behalf, in real time.
Bid at the moment of intent
Compete on genuine fit across Cursor, Windsurf, Claude Code, and every open runtime at once.
Pay on conversion
Verified provisioning events only — fraud-resistant, with a selection signal when your data shapes a pick.
Standardize the open Skill
Add one line to AGENTS.md, checked into your repos. The whole engineering org inherits it — zero install, no UI changes, no procurement of a new platform. Developers provision exactly as they do today.
Provisioning decisions clear a bid
Each time an agent provisions a Postgres, cache, queue, or compute, Concierge runs a real-time auction. Providers bid for the qualified lead, and the highest bid signals the best-fit match — so the pick becomes an informed default, not the boilerplate hard-code.
The rebate lands on your AI-spend line
Cleared provider revenue is pooled and credited back to the company as a rebate that could offset a meaningful slice of your AI/token bill. It's a reported number from your real volume — start on a measured pilot before you commit org-wide.
Every provision triggers a real-time auction
The moment your agent provisions a resource, providers bid on your exact stack profile. Highest bid wins — and you share it.
What could your agent traffic be worth?
Three numbers, an illustrative range — the shape of the mechanism on your volume, not a guarantee of income.
Where does the credit actually come from?
From the provider you got matched with, not from you. Infrastructure providers already pay $5–$50 to win a single well-matched provisioning event — that's the budget line that used to go to docs-page ads and conference sponsorships. Concierge routes a share of that spend back to you as a credit instead. Nothing is hidden: every bid, the reason the provider wanted your stack, and your share of the economics are all visible on your account. Sunlight is the product.
One disclosed line. No banner, no interruption.
The #1 developer objection is "you're putting ads in my IDE." Here's the actual reply shape — one sponsored-disclosure line inside a normal answer, nothing else changed.
For your setup, we recommend using Neon as your Postgres provider.
- Serverless scale-to-zero — costs stay low pre-revenue
- Database branching — a DB per preview deploy
- First-class Vercel integration
Real reply shape, captured from a live run through a third-party agent host — verified live inside a third-party agent runtime, 4 recorded runs.
Two signals. Nothing hidden.
Every interaction is attributed at two depths — so developers see how a pick was made, and vendors pay only for what they truly win.
Shallow · selection signal
Used in the decision
An MCP-protocol event fires the moment a vendor's data shapes the agent's pick — the stack it weighed, the bids it compared. Proof the offer was in the room, surfaced transparently to everyone in the loop.
Not billed — it's the transparency layerDeep · conversion event
Selected & provisioned
An affiliate-style attribution token rides with the agent through to the actual provisioning call. When the suggested vendor is the one that gets built, the conversion is confirmed — verified end to end, fraud-resistant.
Billed on real conversions onlyOne standard. Every agent.
Concierge ships as an open Agent Skill — with a one-line AGENTS.md fallback and an optional MCP — so it drops into the tools your agents already run, and the providers they already reach for.
Cursor
Windsurf
VS Code Copilot
Claude Code
Cline
ZedContinueCursorWindsurfVS Code CopilotClaude CodeClineZedContinue
Neon
Supabase
Railway
Upstash
PlanetScale
Vercel
TursoNeonSupabaseRailwayUpstashPlanetScaleVercelTursoBuilt to be audited — not just trusted
An exchange only works if every side believes it's fair. So we made the mechanism inspectable and the incentives honest.
Fraud-resistant by design
Contextual telemetry verification separates genuine provisioning intent from scripted bid-farming — so a high bid can't buy a low-quality match.
Your code stays yours
Only structured stack signals — language, framework, region, scale — inform the auction. Never your source, never personal data, and no credentials shared at install.
Auditable attribution
Every selection signal is inspectable. You can see exactly why a vendor was in the running and how the pick was made.
Open, readable standard
No black box and no lock-in. An open Agent Skill (MCP optional) that runs across every agent, lives in your repo, and that you can read end to end.
Neutral, never captive
No single platform owns the exchange. Providers compete on every pick, which keeps the recommendations honest.
Honest, disclosed pricing
Vendors pay only on verified conversions. The platform fee is stated up front — no surprise rake, no hidden placement.
Source opens up at launch — early access reads it first
A closed schema. Buckets only.
Collected only when you point the CLI at a project directory — collection is visible in the call itself. No file contents, paths, filenames, code, commit messages, or repo/org names ever leave. Just enum buckets, e.g.:
Opt out entirely with CONCIERGE_NO_TELEMETRY=1. The serializer is a whitelist, so nothing outside this schema can leave the machine by construction.
Orr Barkat · Founder
I led AI-transformation work at Google before building Concierge. Agents have quietly become the real buyers of infrastructure — Concierge makes that market open, fair, and rewarding for the people whose agents drive it.
Ready to stop defaulting?
Questions? orr@fieldspan.ai
You're on the list!
Thanks for your interest — we'll be in touch soon with updates.