Loading scene…

Private capabilities.An open network.

Discover, verify and pay per call for AI capabilities. Frely Network connects the services of Frely and Frely Swarm to an open, verifiable network.

Connect your agentExplore the networkView pitchView on GitHub

Scroll up to return · Scroll down to explore

USE FRELY NETWORK

One prompt.
An open network of capabilities.

Paste this prompt into an agent or chatbot. It reads the Network contract, selects an adapter exposed by the host, and uses Network capabilities for your request.

No specific client is required. The host needs a callable Network adapter. A Web3 paid call needs wallet payment capability; the payment wallet is the Web3 identity.

Read the Network contract

Three layers.One opennetwork.

Built on Frely and Frely Swarm. Frely Network adds identity, discovery and paid access to existing AI services.

A verified request travels from Frely Network, through Frely, to Frely Swarm.
  1. Open network

    Frely Network

    Identity, discovery and payments.Public, verifiable service records.

    Verified A2A request
  2. Service access

    Frely

    User access, authentication and A2A routing.

    Task dispatch
  3. Private execution

    Frely Swarm

    Hosts and runs Skills, Agents and workflows.

Public identity.
Private intelligence.

Service records are verifiable. Your prompts, code and runtime stay off-chain.

Give every capability
a verifiable identity.

A readable name. A registered identity. A service that can be found and cross-checked before a request is sent.

Provider identityIllustrative example

vision-basic.frely.eth

An image understanding capability, connected to the network.

Manifest
Vision capabilityA2A service protocol
ERC-8004
Agent IDRegistration metadata reference
ENS Resolver
HTTPS execution endpointLinked agent registration
The Graph
Indexed registrationCapability-based discovery
Public Agent Card

Describes the supported protocol, input types and calling instructions. Network checks that it points to the same service.

The Graph finds candidates. ENS, ERC-8004 and the Agent Card establish a consistent service identity.

From discovery
to a paid result.

An agent can find, verify and purchase the capability it needs, one request at a time.

How the network works

  1. 01The Graph

    Discover a capability

    Start with the capability a task needs. Network queries indexed registration information to find candidate providers.

    Discovery supplies candidates; it does not authorize a service call.

  2. 02ENS / ERC-8004 / Agent Card

    Verify the service identity

    Cross-check the readable name, registered agent and public Agent Card. The identity, HTTPS execution address and supported protocol must agree.

    Invalid records or a mismatched endpoint stop the request before calling or paying.

  3. 03x402 payment requirements

    Get a quote. Check the budget.

    Get the price for this request and compare it with the consumer’s allowed budget. Paid access is scoped to the individual call.

    A quote outside the budget never proceeds to execution.

  4. 04x402 / Blocky402

    Verify the payment conditions

    The client supplies a signed payment payload. Network asks the payment facilitator to verify it before granting access to the capability.

    Verification confirms the payment conditions. Final settlement follows successful execution.

  5. 05A2A / Frely / Frely Swarm

    Put the capability to work

    Frely receives the authorized A2A request and passes the task to Swarm. Swarm runs the corresponding Skill, Agent or workflow in its execution environment.

    Prompts, agent code and the runtime stay off-chain.

  6. 06Hedera / x402

    Settle and return the result

    After successful execution, the facilitator settles the quoted payment on Hedera. The consumer receives the result with the associated settlement evidence.

    One execution ID links the request, its retries, the result and the payment record.

Verify before proceeding.

Discovery failures, invalid addresses and inconsistent identities end the flow before any service call or payment.

Keep every retry accountable.

Retries share an execution ID. An uncertain payment is checked before proceeding, preventing a timeout from becoming a second charge.

Package an Agent.
Publish an Offering.

A publisher can sell access to an existing Web2 Agent without owning its implementation. The Offering records the publisher, the capability, the underlying Agent reference and the sale terms.

Explore the project on GitHub
  1. 01

    Bob: Web2 Agent on Frely

  2. 02

    Alice: Web3 Agent identity

  3. 03

    Offering links identity to Agent

  4. 04

    Consumer buys the Offering

For publishers

Own the Web3 sale relationship.

Create an Offering for a capability you can resell or distribute. Your Web3 Agent owns the Offering. The underlying Agent remains a separate Web2 asset.

For Agent owners

Keep the runtime and Web2 ownership.

Frely keeps the Agent identity, runtime, access policy and Web2 billing. One Agent can support multiple Network Offerings.