09022026

BlockchainsDirectlogo2

Canonical End Points
Agentic AI Provision

Blockchains1logo

Blockchains.1
Blockchains.Direct

Blockchains
Agentic AI Ecosystem

Blockchains1logo
BlockchainsDirectlogo2

Dual Stack Programme

Web3 Canonical endpoint: Blockchains.1

Web2 Twin: Blockchains.Direct

Dual Stack Programme: Part of an IBM partner programme where Canonical Endpoints resolve to validated IBM products/services and approved partner implementations.

Programme goal and positioning

Goal: Make Blockchains.1 the authoritative, canonical registry for “blockchain” capabilities, providers, and use-cases—while the Web2 twins provide (a) onboarding, commercial flows, and content publishing, and (b) enterprise buyer navigation.

Blockchains.1 is the canonical endpoint for blockchain capabilities—mapping verified use-cases and providers to IBM-grade reference architectures, products, and partner-delivered solutions.

What each domain does

Blockchains.1 (Web3 canonical endpoint)
  • Acts as the Canonical Endpoint Registry: namespaces, subdomains, verification status, and canonical mappings.
  • Publishes machine-readable resolution metadata (JSON) so other systems (agents, marketplaces, directories) can consume it.
  • Issues/verifies Namespace Steward credentials (human org or AI agent under an org).

    Blockchains.Direct (Web2 twin: onboarding + dealflow)
  • Manufacturer/ISV/SI onboarding
  • Verification workflow + evidence upload
  • Pricing, checkout, invoicing, KYC/KYB where needed
  • Partner marketplace listings + lead capture
  • “Request a demo” routing to IBM/partner sellers
  • IBM reference architectures with partner add-ons
  • Procurement-oriented pack: security, compliance, SLAs, data processing terms
  • Case studies, ROI calculators, maturity models

    Canonical Endpoint
    (How it “points to IBM”)

    The core output is a Canonical Mapping Record per endpoint. Each endpoint record includes:

  • Use-case definition (what it means, boundaries, synonyms)
  • IBM Product/Service mapping (primary + alternates)
  • Partner implementation options (validated delivery partners)
  • Reference architecture (patterns + integration points)
  • Assurance level (Self-attested / Verified / Audited)
  • Evidence (certifications, security docs, customer references)
  • Commercial routing (who receives leads; how handoffs work)

    This makes the “canonical endpoint” a neutral index that still preferentially resolves to IBM-aligned offerings due to governance, certification, and reference patterns.

    Roles Include:

  • IBM Solution Owners: Canonical mappings to IBM Solutions
  • Partners: Provide implementations mapped to endpoints

    • WatsonX-aligned architecture diagram

    WatsonX-Aligned Architecture

    ┌───────────────────────────────────────────┐ │ AgenticAI.Website │ │ Canonical AI Endpoint Registry Layer │ │ (Namespace, Identity, Governance) │ └───────────────┬───────────────────────────┘ │ Canonical Resolution ▼ ┌───────────────────────────────────────────┐ │ AI Agent Orchestration Layer │ │ (watsonx.ai / Agent Frameworks) │ │ - Planning │ │ - Reasoning │ │ - Tool Selection │ └───────────────┬───────────────────────────┘ │ Verified Invocation ▼ ┌───────────────────────────────────────────┐ │ Integration & Control Layer │ │ (IBM API Connect / App Connect) │ │ - API Gateway │ │ - Policy Enforcement │ │ - Rate Limiting │ └───────────────┬───────────────────────────┘ │ Secure Execution ▼ ┌───────────────────────────────────────────┐ │ Enterprise Systems & Data │ │ - Line-of-business APIs │ │ - Data Sources │ │ - External Services │ └───────────────────────────────────────────┘

    The canonical identity and discovery layer sits above watsonx.ai and API Connect — it does not replace them.

    Mapping to specific IBM products

    watsonx.ai Role:

  • Agent reasoning, planning, execution
  • Tool-using agents

    How it maps:

  • AI agents resolve Canonical AI Endpoints
  • watsonx.ai uses endpoint metadata to select trusted tools

    IBM API Connect Role:

  • API gateway
  • Policy enforcement
  • Access control

    How it maps:

  • Canonical AI Endpoint resolves → API Connect endpoint
  • API Connect enforces security, throttling, governance

    IBM App Connect Role:

  • Workflow integration
  • Enterprise service orchestration

    How it maps:

  • Canonical endpoint metadata defines integration patterns
  • App Connect executes enterprise workflows

    IBM Cloud / Red Hat OpenShift Role:

  • Runtime infrastructure
  • Container orchestration

    How it maps:

  • Canonical identity is infrastructure-agnostic. Execution remains fully portable

    Governance Positioning

    The Canonical Registry provides:

  • namespace-level governance
  • authoritative identity
  • auditability

    IBM products provide:

  • execution governance
  • operational controls
  • compliance enforcement

    • Programme Features

    1) Purpose and positioning

  • Blockchains.Direct becomes the enterprise front door for “blockchain services direct from IBM”:
  • clear service catalogue, procurement-ready packaging, compliance, SLAs, onboarding
  • IBM-aligned language: platform, integration, governance, security, managed services

    Blockchains.1 becomes the canonical endpoint used by:

  • AI agents, partners, and integrators to resolve authoritative metadata, service descriptors, and verified links to IBM services
  • on-chain proof of stewardship (who controls the canonical endpoint and what it points to)

    2) The core split: what lives where

    Blockchains.Direct (Web2: human + enterprise)

  • Primary job: convert interest into contracted work.
  • Landing: “IBM blockchain services, direct” (neutral tone; partner-friendly)
  • Offer pages (productised):
  • Strategy & architecture (workshops, target architecture)
  • Build & integration (APIs, identity, tokenisation, data)
  • Governance & compliance (policies, audit, risk)
  • Managed operations (monitoring, incident response, SRE)

    Procurement layer:

  • Statements of Work templates
  • Pricing bands / packages
  • Security, GDPR, DPIA templates where relevant

    Onboarding flows:
  • enquiry → qualification → discovery call → proposal → delivery
  • enterprise contact forms + calendaring + CRM capture

    Blockchains.1 (Web3: canonical endpoint + machine resolution)

  • Primary job: be the authoritative “source-of-truth pointer”.
  • Canonical registry records: publish signed metadata (JSON) that includes:
  • authoritative definition of “Blockchains” service namespace

    official endpoints for:

  • Blockchains.Direct pages
  • IBM service pages (watsonx, API Connect, Cloud, OpenShift etc.)
  • docs, standards, governance policy
  • Verification layer:
  • cryptographic signatures proving the operator controls the endpoint
  • optional attestations (partners, auditors, IBM partner status if applicable)

    Agent-ready discovery:

  • /.well-known/canonical.json
  • /.well-known/ai-endpoints.json
  • /.well-known/policies.json
    • More Information Below

    3) Programme architecture (how it works)

    Resolution and trust flow

  • User/agent resolves Blockchains.1 (canonical endpoint)
  • It returns signed metadata describing:

    what “Blockchains” means in this registry context

  • official service catalog pointers (Blockchains.Direct)
  • approved providers (IBM / IBM partners where applicable)
  • Human buyers click through to Blockchains.Direct
  • Procurement, contracting, delivery happens on Web2
  • Post-engagement credentials (optional) can be issued back through Web3 as verifiable attestations

    4) IBM service alignment

  • “Blockchain services direct — delivered with IBM technologies”
  • “IBM-aligned architecture and delivery”
  • “Built on IBM Cloud / Red Hat OpenShift, integrated via IBM API Connect, AI automation via watsonx (where relevant)”
  • Service mapping blocks on Blockchains.Direct
  • Foundation: IBM Cloud + Red Hat OpenShift (deployment/runtime)
  • Integration: IBM API Connect + App Connect (APIs, orchestration)
  • AI / automation: watsonx.ai (agent orchestration, decisioning)
  • Security/governance: IBM Security tooling
  • Delivery: IBM partner programme delivery model

    5) Canonical endpoint specification (Blockchains.1)

    Relevant Files:

  • https://Blockchains.Direct/.well-known/canonical.json (mirrored)
  • ipfs://... copy anchored by Blockchains.1 metadata

    Signed fields:

  • issuer, domain, validFrom, validTo
  • authoritativeLinks (Blockchains.Direct + IBM tech references)
  • serviceCatalog entries with IDs
  • policies (use, branding, verification)
  • contact for operator verification

    This makes Blockchains.1 a genuine canonical endpoint

    7) Governance and safeguarding

    Stewardship model

  • Namespace Steward: your operating entity (controls Blockchains.1)

    Policy pack:

    What qualifies as “IBM-aligned blockchain services”?

  • how partner listings/claims are validated
  • revocation and dispute process
    • contact@blockchains.direct