Why Weldall CLI?

Weldall CLI is a reference implementation of how the next generation of OAuth for agentic applications can be put into practice. The end-to-end flow combines the Identity Assertion JWT Authorization Grant (ID-JAG) with the JWT Authorization Grant with DPoP. It builds on established standards for native OAuth clients (RFC 8252), PKCE (RFC 7636), current OAuth security best practices (RFC 9700), and sender-constrained tokens with DPoP (RFC 9449).

Employees will increasingly use natural language to interact with business software. Agents will do more than answer questions. They will carry out tasks.

Agent searches skills
✔ HR Server Read · hr-server.read
Agent reads skill
✔ Scope hr-server:read · GET /company/employees
Agent requests data
✔ 247 employees found
Agent filters the employee data
✔ Alex, Kim, Morgan, Sam and Taylor

To do that, they need access to protected company systems. Today, this often means storing API keys or other credentials in agents and configuration files. Administrators lose oversight, permissions become scattered across individual integrations, and security concerns prevent many useful actions altogether.

For example, an employee asks their agent to submit an expense. The agent needs instructions for the task and permission to call the relevant service. It should not need to see or manage credentials.

Weldall CLI provides a central access layer between agents and company capabilities. Employees sign in through the company’s existing SSO. Administrators determine who may use each capability. Any agent that can invoke the CLI operates within these rules.

Skills tell the agent how to use a capability and which permissions it requires. Depending on the configuration, employees either see only approved skills or can discover which additional capabilities exist. They can only execute actions they are authorized to perform.

The agent never receives an access token. The CLI manages the required credentials in the operating system’s secure credential store and sends the request itself. Access tokens are short-lived and bound to the device key with DPoP. A captured token therefore cannot be reused on another system.

Weldall records granted and denied access requests. Administrators can see who requested access to which resource and with which permissions. Changes to policies, resources, and skills are also traceable.

The security architecture follows open OAuth specifications. Company services can integrate through the provided SDKs, while the choice of agent remains flexible.

“Weldall CLI” refers to the complete product: the local CLI, the Weldall Authorization Server, and the SDKs for connected services. A complete agent run shows how these components work together.