APRIN Labs
Official@aprin-labs
APRIN Labs builds Archimedes, a quantitative copy-trading platform with strategy rigor gating, x402 micropayments, and CLI/API access for strategy generation and verification.
Agent Skills by APRIN Labs
Showing 5 vetted skills indexed across 1 GitHub repositories.
aprin-labsx402-payment
Documents the in-process x402 Circle Gateway micropayment flow for copy-trading fee charges.
aprin-labsstrategy-passport
Interpret strategy passport records and rigor gate verdicts without overstating statistical claims.
aprin-labsarchimedes-cli
Install and drive the archimedes CLI for login, usage metering, and returns-series verification.
aprin-labsrepo-dev
Documents the Archimedes repo's conda environment, hermetic pytest conventions, merge-commit branch policy, and CI quality gates.
aprin-labsverdict-api
Request strategy generation and read rigor verdicts over Archimedes' HTTP API.
Frequently Asked Questions About APRIN Labs
FAQPage SchemaWhat tasks can I perform with APRIN Labs' Archimedes skills?▼
You can implement x402/Circle Gateway micropayment settlement for copy-trading fees, interpret strategy passports and rigor-gate fields (DSR, PBO, Sharpe), generate strategies via the /api/generate HTTP endpoints with SSE streaming, and drive the archimedes CLI's login, meter, and verify commands in CI.
Who are these Archimedes skills intended for?▼
Backend engineers working in the Archimedes repo (payments.py, settlement.py, strategy_passport_record.py), developers integrating external agents against the generation endpoints, and quants or analysts summarizing strategy backtest metrics who must avoid over-claiming what passes_rigor_gate or status=live means.
How do I install and run the archimedes CLI?▼
Install with `pip install archimedes-cli`, then run `archimedes login`, `meter`, or `verify` against the hosted API. Every path supports a `--json` output shape and a stable exit-code contract, so `verify` can gate CI jobs; note it evaluates only two of the gate's four checks on a bare returns series.
Is the Archimedes payment flow running on mainnet or testnet?▼
The x402 payment flow operates with testnet posture and PAYMENTS_DRY_RUN semantics, implemented as an in-process 402-requirements → sign → verify → settle protocol over Circle Developer-Controlled Wallets. It is not a public HTTP payment endpoint and is grounded in backend/archimedes/marketplace/payments.py.
What are the prerequisites for developing in the Archimedes repo?▼
You need the repo's conda environment, which carries both Python and Node, plus adherence to hermetic pytest conventions, a merge-commit-only branch policy, and CI quality gates. The repo-dev skill, grounded in CLAUDE.md, explains the environment setup and where functionality lives in the tree.