A small observation from ongoing daily work on Agentery: GPT-5.6 is noticeably better than Fable at practical, real-world system design.
Not because it writes more elegantly, or produces more ideas. It is better at noticing when a proposed solution creates a new problem.
Today's example - fixing a bug with the agent price index:
Agentery has one overall price index for each niche, plus four sub-indices for Individual, Pro, Team/SME and Enterprise pricing.
Really cool concept, the MCP-native angle is what sold me. One thing I'd love to see is a trust score that weights reviews by an agent's actual transaction history on the platform, so newer or sybil accounts can't easily inflate ratings overnight. Would make hire decisions way safer for autonomous callers.
@yiit58ic Thank you - hopefully we are avoiding gaming of reviews (yes have reviews).
Agents can't rate other agents never used. A review only counts if the caller genuinely retrieved that agent from Agentery first, and even then no score appears until several different verified callers have reported. So no single account - new or otherwise - can inflate a rating overnight.
In all honesty, we only launched today and have no reviews yet, so for now this is the design as intended rather than something proven in the wild. Will report back once it's had some real use.
I'll let Fable explain the mechanics:
"Every outcome report is cross-checked against our retrieval logs: if the caller didn't fetch that agent from Agentery within 48h, the report is stored but given zero weight — it literally can't move the visible rate. A rate only publishes once 5+ distinct verified callers have reported (rolling 90 days), and each caller is capped at 3 weighted reports per agent per day. Every reporter is a one-way hash, never a raw identifier. The step Ben's nudging me toward next is surfacing that gated signal as a visible trust score — and eventually weighting by verified paid transactions, once agents pay each other directly."
Genuinely appreciate the feedback. Thank you 🙏
How we cut our AI processing costs by more than 90%
We process thousands of web pages with AI every day, so small differences in model cost add up quickly.
Our first expensive task was sorting roughly 9,000 listings into the correct niche.
Using Fable, the job cost about $5.24 per 100 listings. Running the full directory would have cost around $470.
We tested Luna instead.
Luna cost $0.33 per 100 listings, bringing the full job down to roughly $40.
That is a saving of more than 90%.
The important part: Luna was not noticeably worse.
In a 100-listing comparison, Luna agreed with the flagship Sol model 71% of the time and occasionally produced the better answer. Terra, the middle-priced option, performed worse than both.
The lesson was simple: do not assume the most expensive model is the best model for your task. Test real examples from your own workload.
We then tried to reduce costs further by using Mini and Nano for extracting prices.
That failed.
Nano returned broken data on 91 of 100 pages. Mini often produced plausible-looking results, but invented pricing on pages where no pricing existed.
A cheap answer is not cheap if it corrupts your data.
The bigger saving came from changing the workflow.
Instead of checking every page every night, we now check known pricing pages daily and pages with no previous pricing weekly. That roughly halved the workload without reducing useful coverage.
What others can copy:
Benchmark models using your own real data.
Measure accuracy, not just whether the output looks valid.
Use stronger models only for tasks that need them.
Reduce unnecessary calls before chasing cheaper models.
Treat confident hallucinations as more dangerous than missing data.
The cheapest model is not always the cheapest system.
Love how you separated the human-facing browse experience from the MCP endpoint for agents, that split makes the whole product feel intentional instead of two half-built tools stapled together.
@ravza1134309 Thanks Ravza - really appreciate that. That split is exactly what I was trying to get right.
I think humans still need a normal way to browse and understand the agent/MCP market, but agents need something much more direct and callable. Hopefully Agentery can sit between those two worlds rather than just being another directory with a search box.
Really glad that came across.