For immediate release · sample launch day
One door for every model and every agent tool.
Wicket sits between your agents and the models and tools they call. People set the rules once. Agents ask at the gate. Every decision lands in a log.
This page is a mock-up. All names, quotes and numbers are made up for illustration.
What people might say
“I connected my accounts once. Now I see which agent touched what.”
“Risky actions wait for a named approver. The log shows who said yes.”
“One slider picks the cheapest model that still passes our bar.”
Four things it does
Agent passport
Connect accounts once. Revoke any agent in one click.
Quality bar
Route each request to the cheapest model that passes.
Gate and approve
Allow, ask or deny per tool. Risky steps wait for a person.
Audit chain
Each decision joins a hash-chained log.
Questions
Is Wicket a model?
No. It is a control plane. It does not write answers. It decides which model or tool an agent may reach, and at what cost.
What is the difference between consumer and enterprise?
The door is the same. Consumer adds a monthly cap and a passport view. Enterprise adds team budgets, PII redaction, approval roles and the audit log.
Is this real software?
This is a concept with a clickable prototype. It makes no model calls. Its data is scripted, and model prices and scores are samples.
Where does the agent stop?
At a named step, such as “step 3 of 4”. It shows the memory note it used and what happens on Approve and on Deny.
Can I try it?
Open the prototype. It is one file and needs no network.
Boilerplate
About Wicket. Wicket is one front door for every model and every agent tool. People set a budget and rules once. Agents ask at the gate, and risky actions wait for approval. Every decision goes into a hash-chained audit log. Wicket is a concept; the data shown in its materials is sample data.