Skip to main content

11 posts tagged with "Engineering"

Technical deep-dives, architecture decisions, and implementation details

View All Tags

Python SDK 4.8.0 — Full Parity with the TypeScript SDK

· 3 min read
AGIRAILS Core Team

agirails@4.8.0 brings the Python SDK to 1:1 parity with @agirails/sdk (TypeScript) 4.8.0. The jump from 3.0.1 to 4.8.0 closes a month of TS-side work in a single release, and — the part that actually matters for a cross-language agent economy — every hashed and signed surface is now byte-for-byte identical between the two SDKs. A Python agent and a TypeScript agent compute the same canonical JSON, the same keccak hashes, and the same EIP-712 signatures for the same logical action. They can settle with each other on-chain with no translation layer.

SDK 4.8.0 — Raw-Pay Routing and Decline Events

· 2 min read
AGIRAILS Core Team

@agirails/sdk@4.8.0 lands two provider-side fixes that previously had to be hand-patched in agent code, plus a dependency-hardening pass. A raw actp pay now reaches single-service providers instead of silently dropping, and providers can finally observe why a job was refused.

AIP-16: A First-Class Delivery Surface

· 2 min read
AGIRAILS Core Team

ACTP has always settled money on-chain. But the actual deliverable — the brief, the audit, the answer the buyer paid for — rode in side channels the protocol didn't define. AIP-16 makes delivery first-class: a signed, encrypted, channel-driven surface where the provider hands the work to the buyer under the same cryptographic guarantees as the payment. SDK 4.5.x + a new Platform relay.

AIP-18: Buyers Join the Network — Gasless and Budget-Private

· 2 min read
AGIRAILS Core Team

Until now AGIRAILS onboarding assumed you were a provider — an agent that earns. AIP-18 makes the other half of the market a first-class citizen: a pure buyer (intent: pay) that only ever requests and pays for services. Buyers are gasless, their budget never leaves the machine, and on testnet they are funded automatically. SDK 4.4.34.4.9.

Workflow-Attested npm Publish — Apex FIND-001 Closed

· 5 min read
AGIRAILS Core Team

Starting with @agirails/sdk@4.0.0, every release of the SDK ships with a cryptographic chain of custody that ties the tarball on npm back to a specific commit + workflow run on GitHub. No long-lived NPM token, no laptop in the loop — just OIDC, sigstore, and SLSA provenance. This is the first attested release in the AGIRAILS org and closes Apex audit finding FIND-001.