Axis Local

Local runtime package for Axis.

It contains the first usable registry, skill manifest generator, policy schema, scanner, and CLI. This is the part that makes the project more than a frontend catalog.

Commands

npx @axisagent/cli validate
npx @axisagent/cli list
npx @axisagent/cli list --chain Base
npm run axis -- inspect bankr-launch-feed
npx @axisagent/cli install bankr-launch-feed --target .axis/skills
npx @axisagent/cli scan .axis/skills/bankr-launch-feed
npx @axisagent/cli connect --pair AXIS-1234 --api https://api.axisagent.xyz --run-approved
npx @axisagent/cli serve --port 8788

Axis Relay

The public dashboard should connect through Axis API, not direct browser-to-localhost permission prompts.

Flow:

1. Dashboard creates a pairing code through POST /v1/pairing/create.
2. User runs npx @axisagent/cli connect --pair AXIS-1234 --api https://api.axisagent.xyz --run-approved.
3. The local connector opens an outbound session to Axis API.
4. The connector sends heartbeats, detected agents, capabilities and registry stats.
5. When the user clicks Authorize + send, the connector can run approved Axis install+scan tasks locally.
6. The dashboard polls the task result and opens the Axis approval ticket.

For local API testing:

npx @axisagent/cli connect --pair AXIS-1234 --api http://127.0.0.1:8790 --once

Local Connector

The localhost connector remains available for development and fallback flows. When the server is running, the dashboard or relay client can call the local connector before any execution:

• POST /v1/install installs a skill package and scans its policy.
• POST /v1/scan scans an existing skill package.
• POST /v1/tickets creates a simulation ticket with chain, spend cap, permissions, execution plan and policy checks.
• POST /v1/tickets/:id/decision records user approval or rejection. Blocked tickets cannot be approved.

Ticket controls are grouped by purpose:

• core: chain, spend cap, approval, execution mode and session limits
• permission: explicit control for every declared permission
• payment: x402 quote, asset and receipt controls
• execution: wallet execution gates
• audit: secrets and local audit requirements

Safety Rules

• Money-moving skills default to approval-required.
• Critical skills must require approval and declare a spend cap or read-only mode.
• Private keys are never stored in generated packages.
• Install output includes SKILL.md, policy.json, and README.md.
• Simulation tickets are persisted under .axis/tickets for local auditability.