← Back to Research
Invocation
An Invocation is the successful use of a trusted capability to resolve an intent. It is the unit of value in an agentic internet. It is what Heliacon measures instead of traffic.
A completed act in which a consumer, human or agent, discovers a declared capability of an origin, invokes it against a real intent and receives a result that carries its provenance. Attention is spent looking. Invocation is work done.
Why it matters
- The attention economy rewards being seen. The agentic internet rewards being used. They optimise for opposite things.
- An origin that is invoked is load-bearing infrastructure. One that is merely visited is a brochure. Heliacon is built to be invoked.
- Invocation is measurable and honest. It counts resolved intents, where traffic measures only arrival, not usefulness.
In practice
- An agent calls the ask capability to resolve a definition, and cites the provenance it returns.
- A model reads llms.txt, discovers a capability and invokes it to answer a user. The user never visits the site, and that is the point.
- A capability resolving a real question is an invocation. A pageview on a landing page is not.
Not this
- Optimising the origin for clicks, dwell time or impressions.
- Capabilities that look invocable but return unverifiable or unattributed results.
Provenance
| Version | 0.1 |
|---|---|
| Status | Draft |
| Author | Pete Dainty |
| Updated | 5 July 2026 |
| Source | Canonical origin. See its provenance record. |
Related