Hermes Agent,
reading math on every page.
Drop Mathpix via Locus into your Hermes Agent flow as a single skill. Images and PDFs go in, LaTeX, MathML, and Mathpix Markdown come back, billed per call. The shape of the call matches Hermes Agent's skill 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 Mathpix via Locus registered as one skill. The math works because the flow only spends when it actually processes a page.
Read papers, return structured math.
An autonomous research flow ingests scientific PDFs, calls the Mathpix skill page-by-page, and produces a structured Markdown document with equations preserved. No human-managed Mathpix subscription, no rotating API key in flow logs.
Photo of homework → clean LaTeX.
A tutoring or homework-help flow accepts a photo of a student's handwritten work, calls the Mathpix skill, and returns clean LaTeX the next flow step can render. Per-call billing keeps each interaction cheap; idle days cost zero.
Backfill a PDF corpus.
A scheduled Hermes flow walks a directory of technical PDFs, calls the skill on each page, and pushes structured output to a search index. Per-call billing means the spend tracks the corpus exactly — no monthly quota to over-provision.
Make scientific content reflowable.
An accessibility flow runs textbook scans through the skill to produce MathML and semantic HTML for screen readers. The flow only spends on pages it actually processes.
Stop wrapping Mathpix plans into your flows.
Register one skill, connect a wallet, and your Hermes Agent flow gets full Mathpix accuracy on every relevant call. Idle runs cost zero. Page-quota math goes away. That's the entire deal.
- Single Hermes skill
- Full Mathpix accuracy
- Flow caps honored
- MCP + x402 native
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 standard POST endpoint with a typed body — image or PDF in, LaTeX or Markdown out. You register it in Hermes the same way you'd register any HTTP skill — endpoint, schema, per-call price. Hermes uses the price to plan flow budgets and to show what each run will cost before it fires.
Does Hermes Agent need a Mathpix account or API key?
+
No. The gateway accepts x402-signed requests, so Hermes can pay per call from a wallet you connect. No Mathpix account is created, and there's no shared API key to rotate or leak in flow logs.
What happens when a Hermes flow hits its budget cap?
+
The skill returns whatever pages it has resolved so far and Hermes stops issuing new calls. The flow can decide whether to ask the user for more budget or hand off with a partial result.
Can Hermes call this concurrently across many flows?
+
Yes. Per-key rate limits apply with concurrency-fair queueing — a noisy flow never starves another flow on the same key. Practical limits scale with the underlying Mathpix infrastructure.
How is this different from giving Hermes a Mathpix Convert API plan?
+
Convert API plans are sized in monthly page quotas, which don't fit Hermes Agent's per-call cost model. The skill couldn't report a true per-call cost, so Hermes couldn't do real budget planning. The gateway reports an honest per-call cost up front.
Is the accuracy the same as Mathpix direct?
+
Yes. The gateway proxies Mathpix's engine directly, so equation, table, handwriting, and chemistry accuracy match exactly.