Launching today
AgentKey
One-stop live data marketplace for your agent
146 followers
One-stop live data marketplace for your agent
146 followers
AgentKey is a plugin that connects your agent to live external data in one command. Install it into Claude Code, Codex, OpenClaw, or any MCP-based agent and instantly unlock access to search, web pages, social platforms, finance, e-commerce, business and crypto data. No integrations. No setup. Auto failover keeps workflows running.
AgentKey
The auto failover is quietly the best part. One of the search providers had a bad day last month and my research pipeline didn't even notice.
AgentKey
@shirley_mou "didn't even notice" is exactly the bar we set for it. We track latency and error rates per provider and reroute before requests start failing, so if it's working right there's nothing to see. Glad it earned its keep quietly
AgentKey
@shirley_mou Ha, we saw that one. A provider went down for a few hours, traffic just moved over. That's exactly why we built it. Your agent shouldn't stop working because someone else is having a bad day. Good to hear it did its job.
honestly the auto failover part sounds super useful, would be great if there was a way to see which data source it switched to and why, like a quick log or notification. that way its easier to trust the results when something jumps from one provider to another.
AgentKey
@demet44834 Good call, and framing it as a trust thing is exactly right. Two pieces exist today, the console keeps a full log of every api call, and when a provider is having issues we flag it on the agentkey store page. What's missing is the part you're describing, a marker on the call itself saying it got rerouted and why. That's a genuinely good suggestion, adding it to the list.
AgentKey
@demet44834 Love this suggestion. The failover is one of those features you don't appreciate until something breaks. Seeing a small note like "rerouted from X due to timeout" would be great for transparency without getting in the way! Thank you Demet!
Half my agent demos used to die live because one upstream API picked that moment to have an outage. Failover should be table stakes and somehow nobody else ships it.
AgentKey
@jocky Yeah. When a tool breaks on you, you just go find another one. Agents never had that option. No way to discover what else is out there, no place to go looking. So they just die.
That's the gap we're filling. Glad your demos survive now.
@yanshuo Exactly, that’s the missing piece for agents. Congrats on the launch!
AgentKey
@jocky Fair question why it's rare. A single-provider API has nothing to fail over to, so the feature can only exist at the aggregator layer, and most aggregators stop at the billing part. The unglamorous half is aligning providers closely enough that a swap doesn't change your output shape. That part ate way more time than the routing logic itself.
@lxcong Makes sense, the invisible swap is the hard part. Congrats on the launch!
Installing into Claude Code with one command is the right call — most MCP setups still die in config. Does failover switch sources silently, or does the agent get told the data came from a different provider?
AgentKey
@wanarsan_thongklin The agent does get told. Each response includes which provider actually served it, along with the per-call cost, so nothing is hidden from the calling side. The failover decision itself is automatic, but the receipt is right there in the payload.
AgentKey
@wanarsan_thongklin MCPs are incredibly powerful, but we kept seeing people spend more time configuring them than actually using them. We wanted AgentKey to be something you could install and start using with in minutes, not hours :)
Every cool MCP server I found wanted its own key from a service with its own signup and its own minimum spend. The unbundling was exhausting. Glad someone rebundled it.
AgentKey
@tammytan516 The signups and billing were the easy part to rebundle. The rest is where it gets fun: same-type providers are interchangeable so failover is automatic, the integrations are ours to maintain instead of yours, and an intent layer picks the right tool so your agent isn't guessing across the whole catalog. You see one bill, your agent sees one catalog.
AgentKey
Hey PH , I'm Cong, Founding engineer at Chainbase here. I've spent the past few months building AgentKey, a one-stop live data marketplace for your agent, and I want to share the three problems that took us the longest to get right.
1. Tool discovery
We sit on ~1,800 API endpoints. If you dump those into MCP as static tools, the agent burns ~35,000 tokens of context just loading the definitions, and it still picks the wrong tool half the time. So we built our own intent recognition layer: the agent describes what it wants in plain language, like "find trending sunscreen posts on reddit", and a retrieval model we trained on our own catalog maps that straight to the right endpoint. Param schemas only load for the one tool it actually picks. The whole flow runs on about 1,500 tokens, and it stays that cheap no matter how many endpoints we add.
2. Every agent wants to be integrated differently.
Claude Code, Codex, WorkBuddy, Openclaw ... we support 20+ of them and each has its own quirks. Our answer is a split architecture: a lightweight skill on your machine that auto-detects whatever agents you have and keeps itself updated, plus one standardized MCP server in our cloud that's always current. You set it up once and never think about it again. New endpoints, fixes, upgrades all land on the server side, so there's no local upgrade treadmill to babysit.
3. Upstream APIs are flaky.
Providers rate-limit, degrade, and sometimes just die. We do QoS-based traffic shaping and automatic failover between providers, so when one goes down the request quietly reroutes to a healthy one. Your agent gets an answer instead of a 503.
I'm around all day, happy to answer anything about how this works under the hood.