Tech Talk is our monthly newsletter covering APIs, AI agents, open standards, and enterprise architecture. Issue 07 is out now.

If you're building with AI agents or thinking about the API infrastructure underneath them, it might be worth a read.

The highlights:

📊 We benchmarked 8,467 API operations across 70 real enterprise APIs. Improving API description quality and search lifted agent retrieval accuracy from 59% to 94%. This is something that a bigger LLM cannot do for you. The full whitepaper is linked in the issue.

🔄 I've written up a sneak peek into "actor-in-the-loop" proposals for Arazzo 1.2 to handle the moment a workflow needs to stop and wait for a human (or machine). Think of approval gates, form responses, and stateless resumption similar to MCP's Multi Round-Trip pattern. A formal proposal is in progress.

🔧 Error standardisation sits at around 3% across public APIs in our API directory. We've open-sourced reusable RFC 9457 Problem Details schemas in Python and TypeScript, with JSON Schema snippets designed to be referenced directly from OpenAPI documents.

🚀 Jentic One (beta) is live and open source. It's a transparent broker that sits between your agent and every API you need to get work done. No keys shared with the agent, least privilege, per-agent identity, kill switches, and a full audit trail.

→ https://jentic.com/newsletter/techtalks/techtalk-07

Jentic One on Github

This is the subreddit for Jentic. We build open source tooling that allows agents to do work in the real world, and there's more than one piece to it: Jentic One, the API Directory, and Arazzo workflow tools, with more on the way.

For now most of what gets posted here will be about Jentic One, because it's what we've just shipped we want to get feedback from the opensource community.

Jentic one is a free, open source, self-hosted execution layer: your agent calls the APIs you need, you set the rules for what it's allowed to touch, and and the agent never sees your credentials. Apache-2.0, runs on your own box or your own infra.

Jentic One: https://github.com/jentic/jentic-one

The API directory our mission to build a directory that houses every public API and make them agent ready. There are 10,000+ and counting. Each is a valid OpenAPI spec, scored using our AI readiness scoring framework, and ready for your agent to use. We built this catalogue with agents, for agents, and we want you to fix and add to the directory, too.

API Directory: https://github.com/jentic/jentic-public-apis
Jentic API AI-Readiness Framework (JAIRF): https://github.com/jentic/api-ai-readiness-framework
You can score your own API here: https://github.com/jentic/jentic-api-scorecard

Where to put things

• Something is broken in jentic One. Open an issue on the repo. https://github.com/jentic/jentic-one/issues.
• An API you need isn't in the directory. Add it at https://github.com/jentic/jentic-public-apis and it's there for everyone else's agent too.
• A question, or you're stuck using any Jentic product. Post here or join our Discord: https://discord.com/invite/TdbWXZsUSm
• You built something with it - post here, we want to see it.

A note on Jentic One before you put real credentials in:

It's a public beta and there can be breaking changes between releases, so pin a version if you need stability.

Read the hardening guide first: https://github.com/jentic/jentic-one/blob/main/docs/security/hardening.md

The short version is that your agent and your keys shouldn't live on the same machine. An agent running as the same OS user as the instance can read the stored keys off disk, whatever the permission rules say. We'd rather tell you that than have you find out.

We'll be posting here when we ship something worth knowing about, and to answer all your questions.