# Recto Agentic — Phone signing vault for agents > Phone signing vault for agents (iPhone/iPad app by Erik Cheatham.) - Source: https://appshunter.io/ios/app/recto-agentic/id6771544174 (this page in markdown: same URL + `.md`) - Developer: [Erik Cheatham](https://appshunter.io/developer/6771544176) - Category: Utilities, Productivity - Price: Free - Age rating: 4+ - Requires: iOS 15.0 · 25 MB - Released: 2026-05-24 - Data updated: 2026-10-25 ## What is Recto Agentic? Recto Agentic Phone signing vault for agents — a multi-tenant authenticator analogous to Authy for one-time-passcodes, but for signing for agents. WHAT IT DOES You pair Recto Agentic with any service running a Recto bootloader. The service can then ask the operator for permission to perform an action that requires cryptographic signing — fund transfers, capability grants, autonomous-agent operations, anything that needs a cryptographic signature to authorize. When the service requests a signature, Recto Agentic shows an approval card on your phone with the requesting service's branding, the action being requested, the action's scope, and Approve / Deny buttons. You decide whether to grant permission. If you Approve, Face ID / Touch ID prompts you to physically confirm — the signing operation happens entirely on your device, inside Apple's Secure Enclave. The private signing key NEVER leaves your phone. KEY ARCHITECTURAL COMMITMENTS - Phone-resident keys, hardware-bound: Every signing key is generated inside the Secure Enclave with a biometric access control. The key cannot be exported, cannot be copied, cannot be stolen by malware on your phone (Secure Enclave is a separate processor with its own memory). - Per-pairing identity: Every paired service gets its own cryptographic identity. There's no global "Recto account" — there's nothing to hack, nothing to phish, nothing to enumerate. - Cross-device verification at the substrate edge: Every trust artifact (bootloader id, phone id, the bootloader's signing key) can be displayed inline at full length, copied to clipboard, OR rendered as a QR code that any second device's camera can scan to verify the bytes match what's displayed. You can independently confirm that what the app SHOWS you matches what the app would TRANSMIT. - Server identity by key, not by certificate: Recto pins your bootloader's own signing key at pairing. Every card it shows you is signed by that key, and if the server's certificate changes (as certificates do), Recto asks the bootloader to prove it still holds the key before showing anything. No certificate authority, CDN or hosting provider can put a card on your screen. - Zero data collection: Recto Agentic does not collect any data from this app. Every byte stored stays on your device. The only network traffic is to the bootloader URLs you yourself paired with. - Standard cryptography only: secp256k1 ECDSA for signing, P-256 ECDSA via Secure Enclave for device key, Ed25519 for envelope signatures. No proprietary crypto. No hidden mechanisms. USE CASES - Authorize autonomous AI agents to take specific actions on your behalf (sign on-chain transactions within bounded scope; perform capability-bounded ops; consume rate-limited authority) - Approve cryptographic operations from orchestrators or self-hosted services - Cross-device trust verification (display the bootloader's signing key, scan its QR with a second device, confirm they match) - Substrate for any application that needs operator-bounded cryptographic authority Recto Agentic is the substrate. Consumer applications use Recto's capability layer to ask you for permission before they act on your behalf — you approve each request on your own phone, or you don't. ## Is Recto Agentic safe? Not enough ratings yet to assess Recto Agentic. ## Is Recto Agentic legit? Recto Agentic has limited verification signals. The AppsHunter Legitimacy Score for Recto Agentic is 58 out of 100 points across 7 verification signals from App Store and developer data. ## Version history (last 5 releases) ### 1.2.0 — 2026-10-25 Clean up ### 1.1.2 — 2026-10-20 Recto now keeps your phone registered for notifications, recovers cleanly after it has been in the background a long time, and shows when your phone last heard from your bootloader. ### 1.1.0 — 2026-09-22 Recto now verifies your bootloader by its own signing key, not by a certificate that can change without notice. After updating you'll see "Server identity changed — this pairing predates server attestation": open Settings → Unpair bootloader (keep vault), then pair once more. Your vault is untouched. Cards are now signed by the bootloader, and the app no longer re-renders on every poll, fixing a memory climb during long sessions. ### 1.0.7 — 2026-08-07 - Automatic failover across multiple bootloader servers — pairings now carry a failover list, and the app rotates seamlessly if a server is unreachable - Back up and restore your recovery phrase — a biometric-gated export and import ceremony in Settings - Faster approvals — silent push notifications wake the app the moment a request arrives (polling remains as fallback) - Unpair individual services remotely with a signed revocation - Fixed a pairing signature issue affecting some device re-pair flows ### 1.0.5 — 2026-06-05 Fix: demo-mode pairing now completes on devices without biometric enrollment. --- *Data collected daily from the US App Store and indexed by [AppsHunter](https://appshunter.io/). User reviews are verbatim App Store reviews. Ratings, prices and chart positions refresh continuously; this snapshot is from 2026-10-25.*