Abaxx releases Agents++ for cryptographic agent identity

Abaxx Technologies announced Abaxx Labs and Agents++ on May 1, 2026. Agents++ is an open source library for identity, access control and accountability for AI agents. The abaxxlabs/agents GitHub repository was created on April 30, and the @abaxxlabs/agents npm package was published on May 1.

The original sources are Abaxx's GlobeNewswire announcement, the GitHub repository and the npm package. This is not an X-only rumor. It is a real code and package release.

The core idea is straightforward: an agent should not just hold an API key. It should have a cryptographic identity, a verifiable authorization chain and an audit trail showing who allowed it to do what. Agents++ uses DIDs, verifiable credentials, Ed25519 signatures and hash-chained logs. The first target is PostgreSQL, with column-level scope and encryption so an agent can read approved fields, but be blocked before the query reaches the database if it asks for more.

For executives, the important point is not Abaxx alone. It is the pattern. Too many enterprise AI projects still treat agent governance as a prompt or policy problem. That will not hold once agents touch ERP, CRM, payments, customer data or procurement systems. Control has to be enforced in the tool, data and identity layers.

The practical CIO and CISO question is this: can we prove which agent acted, who authorized it, what scope it had, and whether it tried to exceed that scope? If the answer depends on application logs and trust, the control model is too weak.

Agents++ is early. It is not yet an industry standard, and Abaxx naturally links it to its own ID++ and MarketOS direction. But the signal is right. Agent identity is not decoration around AI systems. It is infrastructure.

Companies building agents now should already require machine-readable authorization, delegation chains, scoped credentials, verifiable logs and enforcement close to the data. Otherwise the next wave of automation becomes another round of shared secrets, unclear accountability and audits after the damage is done.

Source: Abaxx Technologies, GlobeNewswire, GitHub and npm, May 1, 2026.