Tethyr Cloud: Open Agent discovery, zero vendor lock-in (AIdeas Semi-finalist)

builder.aws.com

1 point·walmsles··3 comments

I built Tethyr Cloud for the AWS AIdeas competition - it's a B2B agent federation platform addressing a problem I see emerging: agent discovery is fragmenting across proprietary registries with vendor lock-in. The architecture has two parts: open-tethyr (OSS): Agent discovery server implementing the Agent Exchange (AX) protocol draft by Aaron Sempf. Free, decentralized discovery that prevents corporate gatekeeping. Tethyr Cloud (commercial): Trust layer for B2B commerce - subscriptions, rate limiting, usage metering. Built on the discovery network but doesn't own the data. Key design decisions:

Peer-to-peer agent execution - payloads never touch Tethyr infrastructure Stateless JWT validation with <200ms p95 latency Fire-and-forget usage reporting off the hot path (SQS buffering) Dual-API boundary (AppSync for dashboard, API Gateway REST for SDK)

Built on AWS Amplify Gen 2 in 4 weeks. Running costs: $0/month in Free Tier. Full writeup: https://builder.aws.com/content/3Au66gquBesFWDxq83Luj1SzZOk/...

Top 300 projects advance based on article likes by March 20.

Feedback welcome.

Can you explain how

> Built on AWS Amplify Gen 2

leads to

> Zero vendor lock-in

It seems like a contradiction.

The portal is the B2B component for agent monetisation platform I am building. We are also building free and open source agent discovery - boring federated infra servicekind of like DNS - to ensure Agent discovery is free from lock-in and available for everyone - this is the no Vendor Lock-in component. AWS was a choice and its for a hackathon run by AWS so - needed to.

No Vendor Lock-in is the discovery piece Tethyr.cloud is built on. Thats the killer bit that matters - so we all collectively own agent discovery.

Reply on news.ycombinator.com