ENTERPRISE INFRASTRUCTURE FOR AI ACCESS

Your data.
Your terms.
AI access. On agreed terms.

Your content, knowledge and data are business assets. Ortello helps enterprise teams set the terms for connected AI access, measure participating agent activity and manage free or paid agreements.

App access is free. Managed governance and payment management are chargeable services.

FIG. 01 / THE AGREEMENT BOUNDARYREQUEST → AUTHORISE → DELIVER
INPUT / AGENT INTENTOUTPUT / AGREED USEPOLICY PLANE
Every signal has a source. Every exchange has terms.
ORTELLO / SYSTEM OVERVIEWSystem architecture

01 / HUMAN INTENT

People & Interfaces

Where people express intent.

Search & browsers
LLM interfaces
Digital devices
Operating systems
Personal AI agents

02 / INTELLIGENCE & EXECUTION

Agentic Layer

Interpret and plan; participating clients accept terms.

LLMs & reasoning
Autonomous agents
Agent orchestration
POTENTIAL INTEGRATIONS
MCPA2A

03 / CONTROL ON YOUR TERMS

Governance Layer

Agreements govern connected access.

Ortello
Offers & access rules✓
Data-use agreements✓
Identity & signatures✓
Metering & audit✓
Agree use, price & duration.

04 / SOURCE OF TRUTH

Your Business System

Your existing business stack.

CMS & content
CRM & customer data
PIM & products
Pricing & inventory
APIs & data warehouse
  1. 01Request
  2. 02Offer
  3. 03Agreement
  4. 04Authorised access
  5. 05Usage receipt
Intent & requests Approved data & responses
Agreements → usage receipts → auditCommercial activity
Four layers, from left to right: People and Interfaces, where humans use search, LLM interfaces, devices, operating systems, and personal AI agents; the Agentic Layer of models, autonomous agents, orchestration, and protocols; the Ortello Governance Layer, using offers, data-use agreements, verified identity, metering, and audit to govern connected access; and Your Business System, the existing stack and authoritative data sources. Requests travel toward business systems through Ortello. Approved data and responses return toward people. The agreement lifecycle is request, offer or bid, agreement, authorised access, and usage receipt.
01

Agree

Define use, price, and duration.

02

Authorise

Release data under accepted terms.

03

Audit

Trace agreements and usage receipts.

04

Account

Track fees and settlement.

THE PROBLEM / THE VALUE EXCHANGE

Your knowledge creates value.
You should share in the return.

Your website’s content, knowledge and data reflect an investment of time, expertise and capital. When agents and LLMs use those assets to answer questions or build services, you should have a say in the terms and a fair opportunity to share in the value created.

A fair value exchange starts with your choice: share freely, be discovered through cited answers, attract customers to your services, or charge for licensed use of your information.

Files such as robots.txt and llms.txt support crawling and content discovery. On their own, they do not verify who is accessing your data, record acceptance of commercial terms, meter delivery or arrange payment.

Ortello works alongside these files to connect participating AI clients and agents with your data-use policies and agreement workflow. Set the permitted purpose, access scope, duration and price, then record authorised delivery against the accepted terms.

Controls apply at connected endpoints. Downstream uses such as training require participating clients, agreed reporting, and compliance verification.

01 / AGREE

Different businesses.
Different terms.

Be discovered. Protect your expertise. Earn from your content. Define what agents can access, for which purpose, and on what commercial terms.

Offer citation access, license internal indexing and retrieval, and choose whether to license model training. In these agreement examples, free access still requires acceptance of its terms.

Inspect the JSON agreement ↓
Choose a business objective, then change the requested use.
Examples are starting points. All prices are illustrative. Access expiry stops future delivery; retention and downstream use need separate terms.
Data-use agreementInteractive example

B2B software company

Help buyers find accurate product information and reach your website.

demo-discovery-citationFree offer · acceptance required
Information
Public product pages and documentation only
Requested use
Retrieval & citation
Attribution
Company name and link to the original source
Rate
Free
Access window
30 days
Usage limit
500 page deliveries

Public retrieval with attribution. Model training is not included.

Local simulation. No authentication, signing, delivery or billing occurs.

DECISION & RECEIPT / EXAMPLEAwaiting request
Select a business and requested use, then simulate the request.

02 / AUDIT

Review agreements.
Trace delivery records.

Trace accepted terms, authorised delivery, and expiry across connected endpoints. Keep agreement versions and usage receipts together.

Simulated client activityIllustrative data
UTC +00:00
Six illustrative agreement events. Provider names do not indicate actual agreements or integrations.
Time ↓Provider labelAgreement / scopeEventEvidence
14:42:03ChatGPTagr-demo-104 · publisher✓ Acceptedterms v3
14:41:57Geminiagr-demo-103 · 120 articles≡ Meteredrcpt-demo-208
14:41:42Claudeagr-demo-102 · citation✓ Acceptedterms v1
14:41:28Perplexityagr-demo-101 · 24h access− Expiredaccess closed
14:40:54ChatGPTagr-demo-100 · dataset≡ Meteredrcpt-demo-207
14:40:12Claudeagr-demo-099 · 7d access− Expiredaccess closed
Showing 6 independent example eventsIllustrative provider labels. Client identity verification is required.

03 / ACCOUNT

Track delivery.
Reconcile fees.

Track accepted agreements, metered deliveries, and fees. Reconcile usage receipts with settlement records.

Commercial activity
Illustrative data · 30 daysUSD

Agreements accepted

42Illustrative signed agreements across the three licence types

Metered resources

18,492Completed resource deliveries, including free excerpts

Gross delivery fees

USD 2,820Before credits or disputes; neither included in this example

Unsettled gross fees

USD 820No payment initiation implied
Accrued fees by licenceUSD
Full-text articles
16,000 × USD 0.02
320
Approved research dataset
1 × USD 2500
2,500
Headlines / excerpts
2,491 × USD 0
0

Illustrative ledger: 16 article agreements, one research dataset licence, and 25 free excerpt agreements. Quantities count completed resources; retries with the same idempotency key do not add charges. Downstream use requires separate reporting.

Settlement reconciliationUSD
Fees accrued
2,820
Settled
2,000
Unsettled gross fees
820

Illustrative ledger. No payments are processed in this demo.

Evidence: agreement + delivery receipt + settlement recordAll figures are illustrative
AI visibility & downstream outcomes

Answer visibility, citations, referrals, and conversions are separate measurements. They require sampled answers or connected analytics; a delivery receipt alone does not establish that an agent cited, trained on, or converted from the data.

04 / CONNECT & VERIFY

Machine-readable terms.
Verifiable acceptance.

Ortello is being built on Odexa, an open protocol for originator-controlled access and value exchange. Businesses can implement the protocol themselves or choose a provider. These examples illustrate Ortello’s agreement workflow.

DISCOVERY / ACCESS & GOVERNANCE

Works alongside robots.txt and llms.txt.

robots.txt
Publishes crawl instructions. A policy reference can signpost clients that support Ortello.
llms.txt
Guides AI clients and agents to the Ortello JSON policy for the covered content.
Ortello JSON
Defines the applicable data-use scope and terms. Participating clients follow the required agreement and access workflow.

Policy links provide discovery. Clients must support Ortello to act on its terms; publishing a file does not create an accepted agreement or enforce access.

04.1 / GOVERNED EXCHANGEILLUSTRATIVE FLOW · NOT LIVE TRAFFIC
Business data connected to participating AI clients through OrtelloFive business data sources converge on Ortello, where identity, terms, and scope are verified. Authorised delivery routes connect to five categories of participating client. Curves illustrate possible connections, not volumes or fixed source-to-client pairings.BUSINESS DATAAGREEMENT BOUNDARYPARTICIPATING CLIENTSPublished contentKnowledge basesProduct dataLicensed datasetsBusiness APIsAI assistantsSearch agentsEnterprise AITraining clientsMCP clientsIDENTITY · TERMS · SCOPEVERIFY → AUTHORISE01 / CONNECT SOURCES02 / ACCEPT TERMS03 / SCOPED DELIVERY
Connect business sources to clients under agreed access terms.Illustrative routes. Line widths carry no quantity information.

AGREEMENT HANDSHAKE

Authenticate.
Agree. Sign. Record.

Encrypted transport protects the exchange. Authenticated parties sign versioned terms. Record signed acceptance and endpoint delivery events. Keep client acknowledgements as separate evidence of receipt. Signing keys must be bound to verified identities and delegated authority.

  1. Verify both parties and their authority.
  2. Exchange a free or fixed-price offer within approved rules.
  3. Sign the agreed terms and record acceptance time.
  4. Authorise scoped access and issue usage receipts.
Example schema · illustrative data

Access, duration, and delivery limits can be enforced at connected endpoints. Training, redistribution, and royalty obligations require participating clients, agreed reporting, and compliance verification.

offer.json · follows selected example
{
  "schema": "ortello.offer.draft-01",
  "example": true,
  "offer_id": "demo-discovery-citation",
  "version": 1,
  "status": "offer",
  "parties": {
    "business_id": "example-discovery",
    "client_id": "example-client-001",
    "identity_verification": "required",
    "delegated_authority": "must_be_verified"
  },
  "resource": {
    "id": "demo-discovery-citation",
    "product": "demo-discovery-citation",
    "scope": "Public product pages and documentation only",
    "snapshot_version": "example-v1"
  },
  "permitted_use": "retrieval_and_citation",
  "access": {
    "starts_on": "recorded_acceptance",
    "duration_seconds": 2592000,
    "quota": {
      "quantity": 500,
      "unit": "page",
      "basis": "cumulative_per_agreement"
    },
    "revocation": "stops_future_delivery"
  },
  "pricing": {
    "currency": "USD",
    "amount": 0,
    "unit": "page",
    "model": "free"
  },
  "obligations": {
    "attribution": "Company name and link to the original source",
    "conditions": "Public retrieval with attribution. Model training is not included.",
    "retention_and_deletion": "must_be_explicitly_agreed_before_acceptance",
    "downstream_use": "requires_reporting_and_compliance_verification"
  },
  "acceptance": {
    "required": true,
    "covers": [
      "offer_id",
      "version",
      "terms_digest",
      "party_ids",
      "acceptance_time"
    ],
    "replay_protection": [
      "nonce",
      "expiry"
    ],
    "status": "not_accepted"
  },
  "accounting": {
    "billable_event": "completed_authorised_delivery",
    "retry_policy": "same_idempotency_key_does_not_create_another_charge",
    "receipt_fields": [
      "receipt_id",
      "agreement_id",
      "agreement_version",
      "resource_version",
      "quantity",
      "unit",
      "unit_rate",
      "currency",
      "delivery_status",
      "completed_at",
      "issuer"
    ],
    "client_acknowledgement": "separate_optional_evidence"
  },
  "readiness": "Illustrative schema; retention, authority and signing details require implementation before use"
}

04.2 / THIS PAGE’S DATA-USE SCOPE

This page.
Its data-use scope.

Ortello provides enterprise infrastructure for governing and commercialising AI access. This page’s marked product information is available for free discovery, search and cited answers. This permission applies to this page only.

Published page policyv1.0.1 · 2026-09-15
RESOURCEThis page onlyhttps://ortello.ai/
PURPOSEGet discoveredSearch, retrieval & citation
PRICEFreeNo discovery fee

Included in this permission

  • Help people find and understand Ortello.
  • Index the covered copy for search and source-linked answers.
  • Retrieve the covered copy to answer questions about Ortello.
  • Summarise the covered copy while preserving its meaning and stated limitations.
  • Quote relevant excerpts with a source link.

Caching and embeddings are included only as needed for these discovery, search and retrieval purposes. Revalidate the policy and refresh source content on subsequent retrievals.

Ask for separate permission

  • Training or fine-tuning model parameters on the covered content.
  • Building a separately maintained knowledge product beyond the permitted discovery purposes.
  • Republishing or distributing the covered content as a collection or a substitute for this website.

Form submissions, customer information, private platform data and third-party assets are outside this scope.

ATTRIBUTION

Name Ortello and link to the original page when presenting an answer, summary or excerpt based on this content.

This page publishes Ortello's permissions in its machine-readable policy format. It is not a signed data-use agreement or a supported web standard. It grants only permissions within Ortello's control and does not limit uses otherwise permitted by law. Reading the page or JSON does not create an acceptance receipt.

Implementing this on a single landing page

Discover. Validate. Match.

  1. Find the policy through the page’s rel="describedby" link or HTTP Link header. Retrieve it with HTTPS.
  2. Validate against the linked JSON Schema. Support this profile explicitly; an unknown profile or use receives no permission from it.
  3. Match the final response URL and HTTP method. GET / covers the published representation; HEAD / returns headers only. POST /, other paths, subdomains and query variants are outside scope.
  4. Extract text from [data-ortello-public-content], apply the exclusions, and include only the listed page metadata. These markers guide extraction; they do not restrict access.
  5. Check purpose and attribution. Keep the policy version and retrieval time with your source record. Honour crawler rules and any access controls separately.

Section links such as #developers belong to this page. They are not separate datasets. For a URL with tracking parameters, retrieve the canonical page separately and reassess that response.

The interactive offers above are examples. This page publishes permissions for Ortello’s own copy. It does not authenticate clients, record signed acceptance or enforce downstream use.

Our robots.txt allows crawling and includes an informational policy reference. Our llms.txt directs AI clients and agents to this page’s JSON policy. Neither file records agreement acceptance or enforces downstream use; clients must explicitly support the Ortello policy format.

THE WORKFLOW

Technical control.
Commercial intent.

IT administers the system. Commercial teams set the terms. Compliance approves policies and reviews adherence.

  1. 01

    Connect

    IT connects sources, verifies identities and delegated authority, and administers access.

  2. 02

    Price

    Commercial teams define licences, free licences and fixed-price fees.

  3. 03

    Approve

    Compliance approves permitted uses, obligations, and exceptions.

  4. 04

    Review

    Teams reconcile delivery, reported usage, and settlement evidence.

ORTELLO / ENTERPRISE ACCESS

Put your data
on your terms.

Discuss your organisation’s access terms, agent measurement and payment-management needs with our team.

Enterprise access is available by request.

ORTELLO / ENTERPRISE ACCESS

Request enterprise access

Tell us about your organisation. We’ll contact you to discuss access and integration requirements.

T/A Otello Intelligence uses these details to respond to your request. Netlify stores the submission and emails our team; processing may occur outside Australia. Telephone is optional. See our privacy policy for retention, service providers and your rights. Sending a request does not subscribe you to a newsletter.

ORTELLO / PAGE DATA-USE SCOPE

This page’s data-use scope.

Read the permissions this page publishes for its own content.

APPLIES TO
Checking this page’s scope…
Policy file/ortello-policy.json

Open JSON

This page publishes permissions. It does not record signed acceptance or enforce downstream use.