Zerker AI Gateway: route, guard and charge
Apache-2.0 · one Go binary · no server-held key Every agent call, through a door you own. Zerker sits in front of your agent traffic and turns raw calls — plain HTTP or MCP — into something you can catalog, route, guard, watch, and charge for. It never holds a key. $ git clone https://github.com/zerkerlabs/gateway.git $ cd gateway && make dev-auth Copy Quickstart → Watch a request No signup.
- ▪Apache-2.0 · one Go binary · no server-held key Every agent call, through a door you own.
- ▪Zerker sits in front of your agent traffic and turns raw calls — plain HTTP or MCP — into something you can catalog, route, guard, watch, and charge for.
- ▪It never holds a key. $ git clone https://github.com/zerkerlabs/gateway.git $ cd gateway && make dev-auth Copy Quickstart → Watch a request No signup.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,006 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Zerker Gateway |
| Canonical URL | https://zerker.ai/ |
| Publication time | Fri, 07 Aug 2026 15:22:26 +0000 |
| Retrieval time | 2026-08-07T15:30:47.516Z |
| Last seen | 2026-08-07T15:30:47.516Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | twPuJebfZILO · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Apache-2.0 · one Go binary · no server-held key Every agent call, through a door you own. Zerker sits in front of your agent traffic and turns raw calls — plain HTTP or MCP — into something you can catalog, route, guard, watch, and charge for. You run it. It never holds a key. $ git clone https://github.com/zerkerlabs/gateway.git $ cd gateway && make dev-auth Copy Quickstart → Watch a request No signup. No account. Nothing phones home. ingress → gateway → upstream simulated forwarded 0 402 held 0 guard blocked 0 The wire One request. Six checkpoints. Nothing skipped. A call enters the gateway and leaves as an invocation record. Every stage below is enforced in-process, at request time — not configured once and trusted forever.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Zerker Gateway.
Discussion
0 commentsMore from Zerker Gateway
