Hermes Agent,
wired for real contacts.
Drop PayPerQ Contacts Enrich into your Hermes Agent flow as a single skill. Natural-language prompts in, ranked verified LinkedIn profiles out, billed per hit. The shape of the call matches Hermes Agent's tool contract — declare it once, then forget it.
Real Hermes flows that rely on this skill.
Each pattern below is a single Hermes Agent flow with PayPerQ registered as one skill. The math works because the flow only spends when it actually finds a person.
Outreach drafts from a one-line ICP.
A salesperson messages Hermes Agent a description of their ideal customer. The flow translates it into a query, calls PayPerQ, drafts personalized outreach per profile, and waits for human approval before sending.
Hyper-specific sourcing in one prompt.
Hermes Agent runs alongside a hiring manager and accepts criteria the way they'd describe candidates in a meeting. Searches are flow-affordable; one good hire pays for thousands of runs.
Auto-build target maps for any market.
A research-side Hermes Agent receives a market thesis, derives a list of target companies, then pulls verified founder/exec contacts. Results land in a doc with citations and per-profile spend logged.
Pipeline scouting on a schedule.
A scheduled Hermes flow watches funding announcements, pulls leadership contacts at fresh-funded companies, and drops a ranked list into your CRM each Monday. Pay per useful contact, not per platform seat.
Stop wrapping seat licenses into your flows.
Register one skill, connect a wallet, and your Hermes Agent flow gets verified LinkedIn data on every relevant call. Idle runs cost zero. Tool migrations later cost zero. That's the entire deal.
- Single Hermes skill
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no SDR funnel.
How does this register as a Hermes Agent skill?
+
It's a single POST endpoint with a typed body. You register it in Hermes the same way you'd register any HTTP skill — endpoint, schema, price-per-hit. Hermes Agent uses the price to plan flow budgets and to show the user what each run will cost before it fires.
Does Hermes Agent need a long-lived API key?
+
No. PayPerQ accepts x402-signed requests, so Hermes can pay per call from a wallet you connect. There's no shared secret to leak in flow logs or rotate every quarter.
What happens when a Hermes flow hits its budget cap?
+
PayPerQ returns whatever it has resolved so far and stops. Hermes Agent treats this as a normal skill result so the flow can decide whether to ask the user for more budget or hand off with a partial answer.
Can Hermes Agent call this concurrently across many flows?
+
Yes. 100 RPS per key by default; we'll lift it on request. Concurrency-fair queueing means a noisy flow never starves another flow on the same key.
How is this different from giving Hermes a Lusha or Apollo seat?
+
Subscriptions don't fit Hermes Agent's skill model. The skill can't report a true cost, so Hermes can't do real budget planning. PayPerQ reports an honest per-hit cost up front, which is what Hermes was designed to consume.
Is the data compliant?
+
Yes. SOC 2 Type II, GDPR-aligned, opt-out registry honored, contractual restrictions on consumer-marketing use. Designed for B2B prospecting and recruiting flows.