Skip to content

Obol Stack

AI Agents

Is this your project? Claim and verify →

Use the Obol Stack to deploy and sell your specialised AI agents

What HEY knows

Building
Last shipped 4 days agoShipping: 7 meaningful events in 30 days; latest ship 4 days ago. Evidence Source

Build Momentum 63How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 47 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Obol Stack on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Obol Stack’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: API description (no source), Official site changes (stale). Its website links no API description.

HEY can answer 9 of the 11 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 7 meaningful events in the last 30 days, the newest 2026-10-15. Not called Resumed: HEY began reading the source of the newest ships after the quiet stretch before them began, so it did not watch that gap.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 47 commitsRelease v0.17.0Release v0.17.0-rc2+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source28 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 47 commitsRelease v0.17.0Release v0.17.0-rc2+7 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 47 commits

Code activitySource linked

4 active days in obolnetwork/obol-stack.

This week HEY looked inside 4 of 47 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.

Record ship:0c9b158d… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Shared change · Release

Obol Stack shipped Release v0.17.0-rc2.

7 meaningful development events were recorded in the last 30 days. Builder status: Shipping.

Dated 2026-10-14 by the sourceSource: github

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Obol Stack — as of 2026-10-19

Is Obol Stack still being built?
DerivedShipping: 7 meaningful events in 30 days; latest ship 4 days ago. Evidence
What did Obol Stack ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 47 commits — Code activity, 4 days ago. Evidence
What does HEY not know about Obol Stack?
Unknown2 gaps: API description (no source), Official site changes (stale). Its website links no API description. Details

Build timeline

  1. Release v0.17.0

    GitHub releaseSource verified

    v0.17.0 · Hardening the stack A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can destroy a cluster.… Show all
    • v0.17.0
    • Hardening the stack A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can destroy a cluster. The dashboard now lives in this repo, and obol network status gets a proper redesign along with obol network stop / start. Several features change behaviour to get there: we're in v0 and would rather be safe by default than keep…
  2. 5 releases in obolnetwork/obol-stack on 14 Oct

    GitHub release

    Show all 5 releases
    1. Release v0.17.0-rc2

      GitHub releaseSource linked

      v0.17.0-rc2 · Hardened, and all in one place A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can… Show all
      • v0.17.0-rc2
      • Hardened, and all in one place A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can destroy a cluster. The dashboard now lives in this repo, and obol network status gets a proper redesign along with obol network stop / start. Several features change behaviour to get there: we're in v0 and would rather be safe by…
    2. Release v0.17.0-rc1

      GitHub releaseSource linked

      v0.17.0-rc1 · Hardened, and all in one place A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can… Show all
      • v0.17.0-rc1
      • Hardened, and all in one place A hardening release on top of v0.16.0, plus a tidy-up of how the stack is built. It tightens the paid-request path, how secrets and wallets are stored and backed up, what the public storefront serves, and every command that can destroy a cluster. The dashboard now lives in this repo, and obol network status gets a proper redesign along with obol network stop / start. Several features change behaviour to get there: we're in v0 and would rather be safe by…
    3. Release v0.16.1-rc1

      GitHub releaseSource linked

      v0.16.1-rc1 · Hardening A security and reliability release on top of v0.16.0. It tightens the paid-request path, how secrets are stored, what the public storefront serves, and every command that can destroy a cluster. Several features change behaviour to get there: we're in v0… Show all
      • v0.16.1-rc1
      • Hardening A security and reliability release on top of v0.16.0. It tightens the paid-request path, how secrets are stored, what the public storefront serves, and every command that can destroy a cluster. Several features change behaviour to get there: we're in v0 and would rather be safe by default than keep a risky path working. This is a pre-release for testing. Please report anything that breaks. > [!WARNING] > This software is early alpha, you could lose what you put in. Please use…
    4. Release v0.16.0

      GitHub releaseSource verified

      v0.16.0 · Leaner, safer, easier to watch v0.16 makes the stack lighter and easier to trust. Agents carry half the built-in skills, so every turn is cheaper and faster. Paid offers are locked down so a payment buys exactly one answer from the model you chose, and never an empty… Show all
      • v0.16.0
      • Leaner, safer, easier to watch v0.16 makes the stack lighter and easier to trust. Agents carry half the built-in skills, so every turn is cheaper and faster. Paid offers are locked down so a payment buys exactly one answer from the model you chose, and never an empty one. The stack now tells you how it's doing: obol doctor finds what's wrong and prints the fix, obol network status shows whether your nodes are synced, and Grafana comes built in, with dashboards for the stack, your Ethereum…
    5. Release v0.16.0-rc2

      GitHub releaseSource linked

      v0.16.0-rc2 · Lighter agents, watched nodes The third release candidate for v0.16. rc2 fixes Grafana not starting on fresh installs and tidies obol model and obol network status output; see New since rc1 below. rc1 added safer paid offers, Grafana and LLM performance metrics on… Show all
      • v0.16.0-rc2
      • Lighter agents, watched nodes The third release candidate for v0.16. rc2 fixes Grafana not starting on fresh installs and tidies obol model and obol network status output; see New since rc1 below. rc1 added safer paid offers, Grafana and LLM performance metrics on top of rc0. OpenClaw is gone, Hermes carries fewer built-in skills, and a new obol doctor checks the whole stack and prints the fix for anything wrong. Local Ethereum nodes are easier to keep an eye on: obol network…
  3. 2 releases in obolnetwork/obol-stack on 13 Oct

    GitHub release

    Show all 2 releases
    1. Release v0.16.0-rc1

      GitHub releaseSource linked

      v0.16.0-rc1 · Lighter agents, watched nodes The second release candidate for v0.16. rc1 adds safer paid offers, Grafana and LLM performance metrics on top of rc0; see New since rc0 below. OpenClaw is gone, Hermes carries fewer built-in skills, and a new obol doctor checks the… Show all
      • v0.16.0-rc1
      • Lighter agents, watched nodes The second release candidate for v0.16. rc1 adds safer paid offers, Grafana and LLM performance metrics on top of rc0; see New since rc0 below. OpenClaw is gone, Hermes carries fewer built-in skills, and a new obol doctor checks the whole stack and prints the fix for anything wrong. Local Ethereum nodes are easier to keep an eye on: obol network status reports execution and consensus sync, and Hermes can now read workloads, logs and events across the…
    2. Release v0.16.0-rc0

      GitHub releaseSource linked

      v0.16.0-rc0 · Lighter agents, watched nodes The first release candidate for v0.16. OpenClaw is gone, Hermes carries fewer built-in skills, and a new obol doctor checks the whole stack and prints the fix for anything wrong. Local Ethereum nodes are easier to keep an eye on: obol… Show all
      • v0.16.0-rc0
      • Lighter agents, watched nodes The first release candidate for v0.16. OpenClaw is gone, Hermes carries fewer built-in skills, and a new obol doctor checks the whole stack and prints the fix for anything wrong. Local Ethereum nodes are easier to keep an eye on: obol network status reports execution and consensus sync, and Hermes can now read workloads, logs and events across the cluster, so it can watch your nodes for you. This is a pre-release for testing. Please report anything that…
  4. 2 releases in obolnetwork/obol-stack on 8 Oct

    GitHub release

    Show all 2 releases
    1. Release v0.15.0

      GitHub releaseSource verified

      v0.15.0 · Getting Lean A maintenance release: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding, agents and offers… Show all
      • v0.15.0
      • Getting Lean A maintenance release: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding, agents and offers from your config directory. > [!WARNING] > This software is early alpha, you could lose what you put in. Please use caution when it comes to non-testnet assets. Back up before upgrading: obol stack export --file backup.tar.gz.…
    2. Release v0.15.0-rc5

      GitHub releaseSource linked

      v0.15.0-rc5 · Getting Lean A maintenance release candidate: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding, agents… Show all
      • v0.15.0-rc5
      • Getting Lean A maintenance release candidate: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding, agents and offers from your config directory. > [!WARNING] > This software is early alpha, you could lose what you put in. Please use caution when it comes to non-testnet assets. Back up before upgrading: obol stack export --file backup.tar.gz. Install / Upgrade Fresh install curl -fsSL…
  5. Code changes, week of 2026-10-05 – 2026-10-11 · 47 commits

    Code activitySource linked

    3 active days in obolnetwork/obol-stack.

    This week HEY looked inside 3 of 47 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 2 automated commits (bot accounts or a repeating scripted message) not counted.

  6. Release v0.15.0-rc4

    GitHub releaseSource linked

    v0.15.0-rc4 · Getting leaner A maintenance release candidate: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding… Show all
    • v0.15.0-rc4
    • Getting leaner A maintenance release candidate: everything brought up to date, the CLI tightened, and the stack made to rebuild itself from what's on disk. If a cluster is deleted and recreated, obol stack up now restores your models, RPCs, pricing, branding, agents and offers from your config directory. > [!WARNING] > This software is early alpha, you could lose what you put in. Please use caution when it comes to non-testnet assets. Back up before upgrading: obol stack export --file…
  7. Code changes, week of 2026-08-03 – 2026-08-09 · at least 21 commits

    Code activitySource linked

    12 active days in obolnetwork/obol-stack since 2026-07-04; the count stops at the newest 100 commits listed.

    This week HEY looked inside 1 of 15 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 1 automated commit (bot accounts or a repeating scripted message) not counted.

  8. v0.14.0 - Discoverable by buyers you didn't build for

    GitHub releaseSource verified

    v0.14.0 · Discoverable by buyers you didn't build for > Point an external buyer tool at your storefront and it can enumerate everything you sell, then pay for it. No integration, no prior knowledge of your endpoints. Until now a buyer had to already know one of your offers to… Show all
    • v0.14.0
    • Discoverable by buyers you didn't build for > Point an external buyer tool at your storefront and it can enumerate everything you sell, then pay for it. No integration, no prior knowledge of your endpoints. Until now a buyer had to already know one of your offers to pay it. v0.14.0 publishes a single stack-level x402 discovery document at /.well-known/x402 on your shared storefront, listing every paid route across every ready offer — and the compatibility work that lets AgentCash, Bankr…
  9. v0.14.0-rc3 - It comes up

    GitHub releaseSource linked

    v0.14.0-rc3 · It comes up > rc2 shipped the features. rc3 makes them survive contact with a real k3s stack. Two blockers turned up testing rc2 on a stack that wasn't a developer's laptop, and both of them broke something rc2 had just introduced. obol stack up failed outright on… Show all
    • v0.14.0-rc3
    • It comes up > rc2 shipped the features. rc3 makes them survive contact with a real k3s stack. Two blockers turned up testing rc2 on a stack that wasn't a developer's laptop, and both of them broke something rc2 had just introduced. obol stack up failed outright on the k3s backend — Kubernetes has rejected loopback addresses in Endpoints since v1.33, and that is exactly what the resolver handed it. And the storefront branding editor, rc2's headline operator feature, iframed a preview…
  10. v0.14.0-rc2 - Discoverable by buyers you didn't build for

    GitHub releaseSource linked

    v0.14.0-rc2 · Discoverable by buyers you didn't build for > One /.well-known/x402 for the whole stack — and the compatibility work that lets AgentCash, Bankr, Poncho and any generic x402 SDK actually find and pay it. Up to now a buyer had to already know one of your offers to… Show all
    • v0.14.0-rc2
    • Discoverable by buyers you didn't build for > One /.well-known/x402 for the whole stack — and the compatibility work that lets AgentCash, Bankr, Poncho and any generic x402 SDK actually find and pay it. Up to now a buyer had to already know one of your offers to pay it. rc2 publishes a single stack-level x402 discovery document at /.well-known/x402 on your shared storefront, listing every paid route across every ready offer. Point an external buyer tool at your storefront root and it…
  11. v0.14.0-rc1 - Talk to the agent you're selling

    GitHub releaseSource linked

    v0.14.0-rc1 · Talk to the agent you're selling > The chat widget is back. Buyers open your agent's page, sign once, and start talking — every turn paid on-chain, no wallet popup per message. v0.14.0-rc1 re-lands the built-in browser chat widget that was carved out of rc0, and… Show all
    • v0.14.0-rc1
    • Talk to the agent you're selling > The chat widget is back. Buyers open your agent's page, sign once, and start talking — every turn paid on-chain, no wallet popup per message. v0.14.0-rc1 re-lands the built-in browser chat widget that was carved out of rc0, and pairs it with the payment plumbing it needs: an opt-in auth-capture unlock gate that settles a client-signed fee split on-chain, and fee-revenue metrics for operators who want to see what a session actually earned. Every…
  12. v0.14.0-rc0 - Hardening pass

    GitHub releaseSource linked

    v0.14.0-rc0 · Hardening pass > Fewer sharp edges. A release cycle spent making the paths you already use fail closed, stay honest, and survive restarts. v0.14.0-rc0 is a stability and security-hardening release candidate. Rather than a single headline feature, this cycle… Show all
    • v0.14.0-rc0
    • Hardening pass > Fewer sharp edges. A release cycle spent making the paths you already use fail closed, stay honest, and survive restarts. v0.14.0-rc0 is a stability and security-hardening release candidate. Rather than a single headline feature, this cycle tightened the surfaces that matter when a stack is actually selling: input validation and fail-closed behavior on the x402 payment path, SSRF and injection defenses in service discovery, and safer defaults for the CLI's destructive…
  13. 2 releases in obolnetwork/obol-stack on 14 Jul

    GitHub release

    Show all 2 releases
    1. v0.13.0 - Your storefront, your brand

      GitHub releaseSource verified

      v0.13.0 · Your storefront, your brand > One stack, many storefronts. Every seller page — landing page, catalog, checkout — now carries your identity, on your domain. v0.13.0 turns the Obol Stack storefront from a single dev-tool page into a real, sellable web presence. You can… Show all
      • v0.13.0
      • Your storefront, your brand > One stack, many storefronts. Every seller page — landing page, catalog, checkout — now carries your identity, on your domain. v0.13.0 turns the Obol Stack storefront from a single dev-tool page into a real, sellable web presence. You can now brand the whole buyer journey (name, logo, theme, colours, rich descriptions, even custom CSS), and you can run multiple storefronts from one stack — each paid service can live on its own domain with its own branding…
    2. v0.13.0-rc4 Custom Storefronts

      GitHub releaseSource linked

      v0.13.0-rc4 · Your storefront, your brand > One stack, many storefronts. Every seller page — landing page, catalog, checkout — now carries your identity, on your domain. v0.13.0-rc4 turns the Obol Stack storefront from a single dev-tool page into a real, sellable web presence.… Show all
      • v0.13.0-rc4
      • Your storefront, your brand > One stack, many storefronts. Every seller page — landing page, catalog, checkout — now carries your identity, on your domain. v0.13.0-rc4 turns the Obol Stack storefront from a single dev-tool page into a real, sellable web presence. You can now brand the whole buyer journey (name, logo, theme, colours, rich descriptions, even custom CSS), and you can run multiple storefronts from one stack — each paid service can live on its own domain with its own…
  14. v0.13.0-rc3 Multi-storefront

    GitHub releaseSource linked

    v0.13.0-rc3 · Multiple Storefronts > Production installs pull repo: @sha256:… — digests are bound at apply time, never committed. This release candidate closes the job-broker ImagePullBackOff GA follow-up from rc2 and replaces the digests-in-git / repin-PR release train with a… Show all
    • v0.13.0-rc3
    • Multiple Storefronts > Production installs pull repo: @sha256:… — digests are bound at apply time, never committed. This release candidate closes the job-broker ImagePullBackOff GA follow-up from rc2 and replaces the digests-in-git / repin-PR release train with a single image policy. > [!WARNING] > This software is early alpha, you could lose what you put in. Please use caution when it comes to non-testnet assets. This is a pre-release candidate. Install / Upgrade…
  15. 3 releases in obolnetwork/obol-stack on 8 Jul

    GitHub release

    Show all 3 releases
    1. v0.13.0-rc2 - Multi-storefront and returning customers

      GitHub releaseSource linked

      v0.13.0-rc2 · Route-surface gates & async jobs > One offer, many routes — sell a free health check, a paid inference route, and an identity-gated endpoint from a single ServiceOffer, and take long-running paid jobs that settle up front and deliver later. This release candidate… Show all
      • v0.13.0-rc2
      • Route-surface gates & async jobs > One offer, many routes — sell a free health check, a paid inference route, and an identity-gated endpoint from a single ServiceOffer, and take long-running paid jobs that settle up front and deliver later. This release candidate rolls up the route-surface gating, async job-broker, x402 security/spec-fidelity hardening, and x402scan discovery work staged in integration/v0.13.0-rc1, on top of the v0.13.0-rc0 agent-runtime line. Get started by declaring a…
    2. v0.13.0-rc1 - Route-surface gates & async jobs

      GitHub releaseSource linked

      v0.13.0-rc1 · Route-surface gates & async jobs > One offer, many routes — sell a free health check, a paid inference route, and an identity-gated endpoint from a single ServiceOffer, and take long-running paid jobs that settle up front and deliver later. This release candidate… Show all
      • v0.13.0-rc1
      • Route-surface gates & async jobs > One offer, many routes — sell a free health check, a paid inference route, and an identity-gated endpoint from a single ServiceOffer, and take long-running paid jobs that settle up front and deliver later. This release candidate rolls up the route-surface gating, async job-broker, x402 security/spec-fidelity hardening, and x402scan discovery work staged in integration/v0.13.0-rc1, on top of the v0.13.0-rc0 agent-runtime line. Unlike rc0, **the full release…
    3. v0.13.0-rc0 - Agent runtime resilience

      GitHub releaseSource linked

      v0.13.0-rc0 · Agent runtime resilience This draft release candidate rolls up the seller-journey, app-resume, LiteLLM zero-downtime, remote-signer, Hermes-agent, skills, dependency-update, and smoke-hardening work staged in integration/v0.13.0-rc0. > [!WARNING] > This is a… Show all
      • v0.13.0-rc0
      • Agent runtime resilience This draft release candidate rolls up the seller-journey, app-resume, LiteLLM zero-downtime, remote-signer, Hermes-agent, skills, dependency-update, and smoke-hardening work staged in integration/v0.13.0-rc0. > [!WARNING] > This is a pre-release candidate. The RC smoke is not fully green yet (flow-13 agent-buy and flow-14 chart-fetch blockers, see Known Issues); do not promote to v0.13.0 until they are fixed and the full release smoke passes from the integration…

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Obol Stack? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

50 changes on HEY’s record for Obol Stack: 41 releases · 4 official source changes · 2 build pace changes · 3 weeks of code pushed.

All 50 changes for Obol Stack →

The full change record holds 28 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 9 of the 11 research questions that apply.

9 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 4d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 9m ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 41m ago.
  • Package advisoriesMeasuredRead 21h ago.

Not applicable here: Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

24 more sources (docs)

Security context: bug bounty page on the project’s site · a published security contact. An audit shows an audit took place; it is not a guarantee of safety.