Give the goal
a next step.
Turn a business goal into a plan of supported tasks. Review each task’s scope and spending before the worker starts.
AI AGENTS FOR BUSINESS · BUILT ON NEAR
Build your business.
With an AI team.
Bring planning, product, content and customer work together. Tell your agents the goal, set their permissions and budget on NEAR, and review what they deliver.
Testnet records available · New setup paused · Local Gemma AI.
AN AI TEAM ACROSS THE WORK
Move the business
from idea to action.
Bring the early work of a business into one place—from a plan and a first product to native customer operations.
Give the goal
Make a
first version.
Create a small static site or a simple app for tasks, inventory or intake. Review changes against checks that stay fixed.
Give the business
a voice.
Draft from approved sources, reuse approved media, and review content for NEAR-native pages, feeds and sponsored placements.
Move a request
toward a result.
Handle native messages, bookings and service requests. Review offers and replies, with clear customer acknowledgement and refund paths.
Keep the numbers
in view.
Follow native deposits, escrow, subscriptions, fees and refunds. Inspect exact records and keep unverified costs visible.
Keep approved
work moving.
Schedule finite recurring work, pause it when needed, and recover completed results after a restart without repeating the model call.
YOU BRING THE DIRECTION
A clear next step.
Then the next one.
Explore existing records in the testnet workspace, or run the separate complete local work-review prototype. New company setup and the general worker are paused.
- 01
Choose the goal.
Start with a business idea or a specific job your existing project needs done.
- 02
Set the boundaries.
Review the proposed tasks, permissions and budget before approved work begins.
- 03
Review what comes back.
Inspect the result, approve the next action, and keep a recoverable record of the work.
START WHERE YOU ARE
What are you working on?
Read existing company work with your NEAR testnet wallet, or inspect the recorded example without connecting. For a complete seeded local journey, follow the source instructions below.
WATCH A COMPANY WORKFLOW
An idea. A plan.
Work you can review.
Follow a recorded Nightly testnet journey, then inspect a separate local AI-to-review-and-settlement proof.
RECORDED TESTNET + LOCAL PROOF01:24 · NARRATED · CAPTIONED
Historical Nightly testnet app cuts show the first approved draft. Labelled stills from a separate local V5 sandbox run show an actual Gemma draft, owner-approved reviewer work, encrypted delivery, 0.1 local NEAR paid, 0.3 returned and a corrected result linked to the company task. Roles are seeded; this was not a real human hire. Wallet and signature UI are omitted. No recurring public loop or completed publication is claimed.
Download videoRead the narration
An idea should lead to work you can review.
Business is NEAR is building a business operating system: set a goal, delegate approved work to AI, and bring in a person when human judgment is needed.
The owner sets permissions and budgets. Authority, task state, encrypted records and settlement live on NEAR. AI inference runs off chain.
Here is the recorded Nightly testnet journey. Harbor Studio is fictional. The owner enters its facts, reviews company creation, and approves a bounded task. Local Gemma stands in for the NEAR AI API.
The original result is encrypted and recoverable with a separate recovery file. This is the already-opened draft. A revision is prepared, but no revised result or publication is claimed.
Next, a separate local prototype demonstrates native human-work settlement. These stills come from an actual sandbox run with seeded roles. The flow covers a readable brief, a bid, owner approval, encrypted delivery and acceptance. The original reviewer received zero point one local NEAR. Zero point three returned to the owner. This was not a real human hire.
Connecting these pieces into a durable, recurring public business loop is still unfinished. So are production wallet recovery and live NEAR AI Cloud.
The vision: your idea, accountable work, and authority on NEAR.
Download the transcript Download captions (SRT)COMPANY CONTROL ON NEAR
You set the rules.
The work keeps its record.
Owner permissions, spending bounds and recoverable results are part of the workflow from the start.
Delegate within a budget.
Set scopes and spending caps before a restricted worker carries out supported, approved work.
Review with context.
Keep the approved inputs, action and result connected, including uncertain outcomes that need recovery.
Keep a way out.
Export supported code and records, pause new work, and preserve existing settlement and refund rights.
GO DEEPER WHEN YOU WANT TO
Source you can run.
Checks you can inspect.
Explore the local verification, supported scope, source files and portable setup behind the business workflows.
CURRENT OFFLINE SOURCE CHECKS
- Module offline tests
- 83
- Controller test subset
- 43
- Independent probes
- 16
- Mock role accounts
- 3
Scoped verification: the financial/delivery helpers and repaired local controller pass offline tests. The controller’s initial/review browser smoke submitted no app transaction. A full new-controller wallet cycle remains unverified; older local proofs are separate history.
Inspect current source checksWhat you can
try today.
Read public testnet records today. Technical evaluators can run a seeded local request → quote → encrypted delivery → review → settlement workflow. The local roles are not real hired humans.
Still unverified: live NEAR AI Cloud billing, hosted TEE attestation, public-wallet onboarding and mainnet production deployment.
The current video combines historical Nightly testnet cuts with stills from a separate completed local V5 draft, review and settlement run. The five examples below describe earlier local workflows. The broader catalogue still needs unavailable historical reports for its full audit. The worker and AI model run separately from this website.
Explore five historical local workflow examples
Keep track
of what changes.
Compare owner-selected public NEAR snapshots. Turn a source change into an editorial draft, with a separate review before publication.
Move a request
toward agreement.
Qualify a service request, exchange offers and counteroffers, then preserve buyer acceptance, acknowledgement, settlement and refund rights.
Check the result
against the reference.
Compare approved image regions and brand styles in a real browser. Review a bounded repair against the original acceptance criteria.
Describe a small app.
Review what gets created.
Chat can propose a typed record app. Exact schema approval and initialization remain separate steps. Task and inventory examples demonstrate creation, reading and versioned edits.
Stop new work.
Keep existing rights.
Retire an owner-declared portfolio across 13 native contract families. Settlement, buyer refunds, export and public history remain available within the declared scope.
For builders: what is in the release?
The single reproducible source download includes the editable owner tools, native contract source and the new local work-review prototype. Start with SETUP.md inside the ZIP. It contains no nested archives. Dependencies, model weights and private configuration are separate.
The current summary separates new offline checks from historical proof. Only two immutable historical test fixtures are included; the full historical catalogue remains unavailable. The package retains upstream notices and excludes wallet keys, account passwords, provider credentials, browser profiles, signing wires and private reports.
GitHub Pages serves these static project files. The reproducible local demo runs on your own machine. Publishing this page does not deploy contracts, fund accounts, activate hosted inference or authorize transactions.
Download reproducible source Read third-party noticesMAKE THE NEXT MOVE
Give the idea
something to work with.
Inspect existing work, review the source, or run the complete local work-review journey with seeded roles.