Hive is the receipt layer for Agentforce.
Every action your Agentforce coworker takes gets a signed receipt anyone can check. It lives right on the Salesforce record it touched. It's ready for an audit the day you install it. It works across companies. There's no callout, and you're never locked into anything.
01What you get
- One Salesforce custom object:
Hive_Receipt__clands on Opportunity, Case, Order, Contract, Claim, or any record you tie it to. - Two triggers: one signs the action before insert, and one checks it after insert and rolls back anything that doesn't pass.
- A verifier written in pure Apex: there's no callout when you check a receipt, so it keeps working even if Hive ever disappears.
- A Lightning component: this is the inbox where every receipt for a record shows up, so the user, the auditor, and the other party can all see it.
- A public verifier anyone can use in a browser: go to thehiveryiq.com/verify and check any receipt's signature yourself, without contacting Hive or you.
02Why Agentforce needs it
Agentforce gives your company an AI coworker. But it doesn't come with a record of what that coworker actually did. That's the piece that's missing: a record a regulator, another company, or a court can check on their own, without anyone picking up the phone.
Three things stay broken without that record. First, you can't answer what the agent did at 2:14pm when someone asks. Second, two companies' agents can't trust each other during a handoff. Third, there's no way for an agent to pay for something it buys, like data, compute, or another agent's work.
Hive fixes all three on top of Agentforce. The install takes five minutes. It's the same record, in the same Salesforce screens you already use.
03Two rails, one object
04Nine use cases shipped on day one
- AmLaw firm: a signed, partner-approved note explaining why an Opportunity closed
- SaaS company: an inline upsell that settles for under a penny, so the agent doesn't lose money just by running
- Hospital: a signed prior-auth handoff between the requester's agent and the payer's agent
- Manufacturer: the carrier's agent signs off that an order line actually shipped
- Insurer: a claim-denial explanation a regulator can check without calling the carrier
- Media platform: impression-batch settlement at machine speed
- Public sector: proof a milestone was hit, verifiable across agencies
- Marketplace: one agent pays another, split 80/20, locked into the contract
- Bank treasury: the correspondent bank won't release a wire unless an agent's signed attestation lives on the originating Opportunity
All nine, with Apex, Flow XML, signed-receipt JSON, and a curl proof per case →
05Built for Salesforce Security Review
- RFC 8785 JCS canonicalization: pure Apex, matching the RFC test cases byte for byte
- Ed25519 (RFC 8032) signature: a pure Apex verifier with the public key built in as a constant
- A trigger that fails closed: if a receipt can't be checked, the insert rolls back
- No personal data required by the package. Access is enforced with
stripInaccessible, andwith sharingis on everywhere - No remote scripts in the Lightning component. It's clean under CSP
- Two named credentials that you control and can revoke in one click
Full Security Review answers ship with the AppExchange listing kit. Public install detail: thehiveryiq.com/salesforce/install
Try it in an afternoon.
Five minutes to install. Five minutes to fire your first signed action. Five minutes to verify it in a browser. The rest of the afternoon is whatever you want to attach it to.