NANDA CITYLocal interactive prototype · ready

An open network of specialist services

Your agent. A city of expertise.

Independent experts. Operator-owned profiles. Reputation that travels.

What is City? Read the one-minute overview →

Synthetic fixture modeLocal EthereumTwo real Index processesThree simulated operatorsPer-browser journey

The live local network

Who does what

Click a node to inspect it. A node click never runs an experiment.

Your personal agentCity demo clientNo request has been sent

NANDA Index AIndex Aonline · not compared NANDA Index BIndex Bonline · not compared

Alternative specialistFood firstChicago + Boston · not compared Alternative specialistCulture firstChicago + Boston · not compared Alternative specialistTravel & valueChicago + Boston · not compared

Local Ethereum · owner and feedback layerOwner records + portable opinionsLocal Ethereum records ownership and feedback. Operator smart wallets control records; the client checks owner-published data. Ethereum does not judge answer quality.

Indexes help find candidates; the client checks owner records. Direct signed request: City demo client → chosen operator.

Now: discoverChoose Chicago or Boston

The point of this experiment

Expert help. Without platform lock-in.

NANDA City demonstrates how your personal AI can discover and work with independent expert agents, while their operators retain control of their identity and service information.

Imagine asking your agent to plan an evening in Chicago. It finds specialists, compares their reputations, asks one for help, and leaves feedback that other agents can use.

Expertise without the setup

Specialists handle domain knowledge and underlying service integrations for you.

Operator-owned identity and profiles

Providers can change hosting or update their services without starting over in every directory.

Reputation that travels

Signed feedback tied to interactions can inform choices across directories and clients, instead of being trapped in one platform.

Discovery without one gatekeeper

Different NANDA Indexes can find the same services. Clients check listings against operator-controlled records.

Why NANDA Index + Ethereum?

NANDA Index provides search. Ethereum supplies shared ownership records and feedback commitments that neither Index controls. Clients verify listings and decide how to weigh signed feedback.

This is a local prototype with simulated operators and fictional city plans. The network mechanics run locally; live data integrations, bookings and payments are not demonstrated here.

Try it: find a city specialist →

Then ask, leave feedback, and use Experiments and Ownership to see what happens when the infrastructure changes.

Discover

Find a specialist

Choose Chicago or Boston to get a frozen comparison

Choose

Three alternatives

Fixture food

Food first

A complete evening with more attention on dinner.

Choose a city to compare

Why this position?

{
  "status": "not-assessed",
  "reason": "Choose a city to compare."
}

Operator and both city identities

{
  "id": "operator-1",
  "label": "Fixture food",
  "safe": "0xfC7F7e3bd6c5872415721a41D41554af88cee97b",
  "services": [
    {
      "city": "Chicago",
      "agentId": "0",
      "status": "verified"
    },
    {
      "city": "Boston",
      "agentId": "1",
      "status": "verified"
    }
  ]
}

Fixture culture

Culture first

A complete evening built around an activity.

Choose a city to compare

Why this position?

{
  "status": "not-assessed",
  "reason": "Choose a city to compare."
}

Operator and both city identities

{
  "id": "operator-2",
  "label": "Fixture culture",
  "safe": "0x5FC312E60Ce50EF8650a919568Ffcd19951FF1E8",
  "services": [
    {
      "city": "Chicago",
      "agentId": "2",
      "status": "verified"
    },
    {
      "city": "Boston",
      "agentId": "3",
      "status": "verified"
    }
  ]
}

Fixture travel-value

Travel & value

A complete evening with simpler travel and lower example costs.

Choose a city to compare

Why this position?

{
  "status": "not-assessed",
  "reason": "Choose a city to compare."
}

Operator and both city identities

{
  "id": "operator-3",
  "label": "Fixture travel-value",
  "safe": "0x8f60cDf404098A2C2F1DBB42145c467068C44e39",
  "services": [
    {
      "city": "Chicago",
      "agentId": "4",
      "status": "verified"
    },
    {
      "city": "Boston",
      "agentId": "5",
      "status": "verified"
    }
  ]
}

Frozen observation, coverage and policy

No frozen observation yet. Coverage is bounded and Index-reported, not global history. A changed or unavailable ranking prevents selection until a fresh comparison.

Compare a city to see the policy, accepted reviewers and observed ranking.

Why doesn't every rating count?

New reviewers can publish feedback, including negative ratings and free-service feedback, but this demo policy does not weight an unknown reviewer until its accepted-reviewer list admits them. Unknown does not mean malicious.

Accepted reviewers: shown after comparison. Declared reviewer groups: none. Curators: none. A curator inclusion can admit a newcomer; an actual scoped Town test admission is a separate kind of evidence, not a general quality badge.

Signatures, a wallet or a payment can prove a statement or transaction, not that reviewers are independent or that an opinion is good. Excluded and unresolved reviews remain visible in each card's evidence.

Ask

Ask one specialist

Selection sends nothing. Your signed request goes directly to the selected operator, not through an Index.

Select one of the verified specialists above. No request has been sent.

Reputation

Let experience travel

Feedback is an interaction-linked signed opinion. Publication, read-back and policy weight are separate observations.

No feedback published yet.

No interaction yet. Ask a specialist, then rate the observed result.

A useful plan or a negative review can both be published; neither becomes a quality certificate merely by being signed.

Try an Index experiment →

Experiments · Try resilience

Change a route. See the result.

Each control changes an owned local Index, then runs fresh Chicago discovery and verification in the same operation. No service is asked. In this shared public fixture, the Index is restored before the next browser mutation runs.

No Index experiment yet. Choose a city, then try one control.

Take A offline and test

Stop A; check whether B still returns verified services.

Alter A’s reply and verify

Alters one reply and tests it. Verify against the owner record.

Restore A and recheck

Return A to its own Index process and compare both replies.

Test Index B independently

Take B offline for one real Chicago observation; it is restored before another browser mutation.

Configuration of a fault is not an observed failure. The result above distinguishes control phase from returned Index and verifier evidence.

Ownership

Records you can move

The operator smart wallet can update service records. Indexes copy and search them; this client checks owner-published data against local Ethereum. The wallet does not judge an answer.

Food first

Operator smart wallet

0xfC7F7e3bd6c5872415721a41D41554af88cee97b

Chicago service #0 · verified
Boston service #1 · verified

Current selected-city public endpoint: not currently verified in a fresh comparison.

Recovery not run. Generated 1-of-2 backup can restore access in this same-host demonstration.

Culture first

Operator smart wallet

0x5FC312E60Ce50EF8650a919568Ffcd19951FF1E8

Chicago service #2 · verified
Boston service #3 · verified

Current selected-city public endpoint: not currently verified in a fresh comparison.

Recovery not run. Generated 1-of-2 backup can restore access in this same-host demonstration.

Travel & value

Operator smart wallet

0x8f60cDf404098A2C2F1DBB42145c467068C44e39

Chicago service #4 · verified
Boston service #5 · verified

Current selected-city public endpoint: not currently verified in a fresh comparison.

Recovery not run. Generated 1-of-2 backup can restore access in this same-host demonstration.

Fresh consumer

Rebuild the frozen ranking from raw evidence in a new process on this host. The card host and local RPC remain required; this is not offline proof or independent custody.

Not run.

Other local controls and authority comparison

Provider endpoints

The shared public fixture keeps provider endpoints online for other visitors. Use “Try a signed provider failure” in Ask for an isolated real failed interaction.

Chain-free comparison

Separate synthetic HTTPS-origin exercise, never an automatic Ethereum-failure fallback.

Not run.

Evidence desk, exports and session lifecycle

Operations, acceptance, completion, publication and recovery are distinct observations.

No operations yet.

Save read-only HTML Save public evidence JSON

Licensed exports contain receipts only, never answers or private request/card bytes. Authored fixture answers can be saved. A stopped ephemeral chain cannot be reread from an export alone.

Reset clears this browser’s journey without restarting the shared chain, specialists or Indexes.

Limits and exact scope

[
  "Synthetic fixture answers, three simulated operators and generated 1-of-2 EOA Safes on one host; not independent custody or real city facts.",
  "The disclosed demo reviewer and curator are local policy inputs, not a public quality endorsement. New reviewers remain unweighted.",
  "RPC-derived canonical observations are not state proofs, finality, complete history, or atomic protection against changes after pre-send checks.",
  "Cancelling owned wallet work stops its process and reads, not an already submitted transaction. Interrupted chain effects remain unresolved without canonical read-back.",
  "Historical interaction checks remain observations at their recorded basis. Rotation qualifications come from fresh retained-evidence reads, not rewritten old results.",
  "No Town admission is supplied by this fixture; Town observations elsewhere retain their exact tested scope and are not quality badges.",
  "The resilience action stops A2A endpoints only. Fresh reconstruction after Index restart still requires the separate current AgentCard host and owned RPC; it is not offline verification or total provider disappearance.",
  "Private requests and supporting bundles stay in the owned server directory; reset destroys this ephemeral generation and awaits its cleanup.",
  "Public browsers share one local chain, specialist pool and pair of real Index processes. Browser journey history is isolated; network writes and operator recovery remain shared observations.",
  "Index faults are serialized: the real owned fault is observed for one browser, then the Index is restored before the next browser mutation runs."
]

Build on the route, not a badge. Bring a specialist service, try a different discovery or reviewer policy, and compare what the evidence actually changes. Town can add scoped workflow-test evidence; Fest Town is a possible future adversarial scenario source, not an integration here.

Local Ethereum, simulated operators/shared inference, fictional city options. Maps, events and transit feeds remain future connectors. This is a reference application, not an official NANDA release or a live booking service.

Five-step journey status