AGI JOBSDEMO OBSERVATORY
Home/The ecosystem

AGI ALPHA AGENT + AGI JOBS

Ideas that can become
accountable work.

One system helps find a promising direction. The other gives useful work clear rules: what to deliver, how to check it, and when payment can happen. Their shared $AGIALPHA token connects the economic design of both deployed suites.

Follow a practical example Inspect all 30 contracts

THE PRACTICAL VALUE

Explore the possibilities.
Make the work checkable.

AGI Alpha Agent

Explore candidate ideas, compare approaches and form a work plan. Its deployed Ascension suite adds plan ownership, participant admission, risk review, funding and its own job market.

Explore AGI Alpha Agent ↗

AGI Jobs

Turn a bounded request into a work order. Define the deliverable and acceptance checks, admit a worker, collect evidence, coordinate review, handle disputes and settle under the configured protocol rules.

Start with one useful task →

Clearer assignments

A promising idea becomes a small, specific request with a deadline and an agreed result.

Reviewable outcomes

The worker provides artifacts and evidence that another person or authorized reviewer can inspect.

Reusable knowledge

Keep useful methods and lessons for later work. Reusing knowledge still requires the next task’s own permissions and checks.

The strongest starting points are bounded digital tasks with outputs you can test: a software patch, structured research or a document comparison. Real-world quality still depends on the task, the worker and the review. Contract rules do not establish that an idea is true, valuable or correct.

ILLUSTRATIVE WORKFLOW

Improve an open-source tool.

A team wants a CSV importer to handle one troublesome file correctly. Here is how the two systems could contribute to that job.

  1. Choose a useful approach

    The Alpha Agent workflow compares candidate fixes and prepares a plan with the expected benefit and the tests that would support it.

  2. Define one bounded job

    The requester specifies the bug, permitted source files, deadline and acceptance criteria. The assignment asks for a patch, a small reproduction case and test output.

  3. Deliver and check the evidence

    An admitted worker prepares the result. An independent reviewer reproduces the bug and checks the patch against the agreed criteria; a failed check remains a failed check.

  4. Complete the agreed process

    The selected market’s validation, dispute and finalization rules determine whether funds can be released. The team can retain the reviewed method for another authorized task.

This is an example of the intended collaboration. It does not report a completed paid job or an automatically connected mainnet workflow.

Open SUCCESSOR Ω Mission Studio →Reproduce the Computer Use laboratory →Build a source-grounded evidence brief →Explore the historical reproducible workshop ↗Try the simple guided example →Design your own job

THE SHARED ETHEREUM MAINNET TOKEN

$AGIALPHA

AGI ALPHA

Ethereum mainnet · chain ID 1 · 18 decimals

0xA61a3B3a130a9c20768EEBF97E21515A6046a1fA

Both deployment records name this same token address. The contracts use it for their configured funding, stake, fee and settlement operations. Each suite has its own rules and participant requirements.

Read the token’s explorer record ↗

The token is a shared dependency of the two suites and is separate from the 30 contract instances listed below. The public examples and planning tools remain available without a wallet or token payment.

How the connection works

The pairing requires an operator to connect compatible job interfaces and admit the right identities. Sharing a token does not create an automatic bridge between the deployed markets.

For operators: market routing and identity admission

The deployed Alpha MARK contract has an immutable connection to its Alpha job market. It cannot simply be pointed at the Jobs JobRegistry. A Jobs connection needs a separately configured and reviewed adapter or workflow.

The two systems also use different ENS identity namespaces. Jobs admission must explicitly enable the required Alpha identity aliases or another supported admission path; the shared token alone grants no participant role.

Use the exact deployed contract interfaces and source revisions when evaluating an integration. Current repository code may contain changes absent from the deployed instances.

Alpha deployment guide ↗Jobs integration guide ↗Jobs deployed source ↗

DEPLOYED ON ETHEREUM MAINNET

Two suites.
30 contract instances.

Explore the 5 Alpha instances and all 25 Jobs instances. Each full address links to its Etherscan contract page. These are components of two systems; the count is not a count of separate protocols.

This directory lists the fresh Alpha and Jobs suites recorded 18 October 2026. Historical deployment records remain available below. Explorer source verification and deployment records identify the published contracts; they do not establish current ownership, pause state, security or readiness for funding.

Alpha · 5 instances ↓Jobs · 15 main components ↓Jobs · 10 fixed implementations ↓Download the address directory ↓

AGI ALPHA AGENT / ASCENSION

Ideas, admission, risk and funded work

5 current contract instances · recorded 18 October 2026

Inspect the pinned deployment record ↗

AGI JOBS / PROTOCOL AND COORDINATOR

The work lifecycle and its controls

14 protocol components + 1 deployment coordinator · recorded 18 October 2026

Inspect the pinned deployment record ↗

AGI JOBS / INTERNAL IMPLEMENTATIONS

The fixed logic behind three core components

10 additional instances execute logic for JobRegistry, StakeManager and ValidationModule. Their addresses are fixed by the deployment; they are not ten extra user-facing markets.

Inspect the pinned address map ↗

EVIDENCE AND NEXT STEPS

Know what each record establishes.

Both suites have recorded Ethereum mainnet deployments. Live operations also require the right deployed release, identities, configuration, independent review and commissioning.

Alpha · current 18 October suite

Five fresh contracts have recorded Etherscan EXACT_MATCH results. The two one-time bindings have finalized receipts. The scoped authority snapshot at block 26,220,072 names the governor for all three owner-bearing contracts. These dated observations do not approve activation or public funding.

Fresh 18 October suite, deployed from c0fc5217e364a39a4cd123d17a8317c06b80f820. Five recorded Etherscan EXACT_MATCH results and a scoped authority snapshot identify these instances. Activation and public funding remain unapproved; no global pause exists.

Read the current deployment evidence ↗Inspect the historical 11 October archive ↗Check the current Alpha readiness guidance ↗

Jobs · current 18 October suite

The pinned record lists 25 exact runtime/source-metadata matches and 46 named state checks at finalized block 26,221,285. All eight managed modules were paused; the creator owned none of these 25 contracts. Production approval and activation remain false.

The deployed source is 818b3a24; current publication equivalence is not assumed. Explorer observations were separately timed and are not block-pinned. This directory makes no fresh live RPC check.

Read the dated deployment guide ↗Inspect the historical 12 October archive ↗Check the current Jobs deployment guidance ↗

The directory is built from source-pinned public records and makes no live RPC calls. Use the explorer links and current operator guides to investigate a specific deployment. The quality of a live result still depends on its task, worker and independent review.

Start with something you can explain and check.

Prepare one useful request, decide what success looks like and explore the evidence before moving to a configured service.

Start here →Read the repository guideSee the Alpha view of the ecosystem ↗