Specification
ABIS Public v0.1 concept, terminology, scope, architecture, examples, governance, and roadmap.
Explore the SpecificationBeyond
Zero Click.
クリックから、ビジネスを解放する。
Legacy web interfaces and cursors transition into blue interaction flow.
- Human Intent
- AI Agent
- Business
- Business Outcome
- BOOKED
- PAID
- ORDERED
- SUBMITTED
- CONFIRMED
Brand Concept — ABIS — Agent Business Interaction Standard
The Internet was built on clicks.
The Agent Era runs on intent.
01THE OLD MODEL
The Internet
Was Built
Around Clicks.
For decades, doing business online has meant operating interfaces.
Finding pages. Comparing options. Filling forms. Moving between systems. Completing transactions one screen at a time.
01Search↗
02Click↗
03Navigate↗
04Compare↗
05Fill↗
06Book↗
07Pay↗
08Confirm↗
AI Agents change that assumption.
02THE SHIFT
From Human Operation
to Human Intent.
THE INTERFACE ERA
Human / Interface /
Website / App / Business system
THE INTENT ERA
Human Intent / AI Agent /
Business Interaction / Business Outcome
Humans no longer need to operate every interface themselves. They can express intent and delegate execution to AI agents.
But removing the click
does not remove the
business interaction.
03THE PROBLEM
Technical Success
≠Business Success.
Technical success does not guarantee business success. HTTP 200 does not mean user intent was achieved.
An AI agent can execute a system successfully and still fail to reach the business outcome the user intended. ABIS is concerned with what actually happened in the business interaction—not merely whether execution completed.
A system can execute successfully while the intended business result is not achieved.
AI agents need more than execution status. They need a common way to understand what happened in the business interaction and what outcome was actually achieved.
04INTRODUCING ABIS
A COMMON WAY TO UNDERSTAND
Across agents.
Across protocols.
Across businesses.
ABIS is an interoperability framework designed to provide a common way to represent Business Interactions and Business Outcomes across different AI agents, protocols, and business systems.
AI agentsExisting protocols / executionBusinessBusiness InteractionBusiness Outcome
A conceptual relationship, not a required middleware architecture.
05BUSINESS INTERACTION
Business
Interaction
What happened between the agent and the business?
ABIS treats the business interaction itself as an explicit shared concern across agents, protocols, and business systems.
01
Reservation
02
Purchase
03
Application
06BUSINESS OUTCOME
TECHNICAL EXECUTION✓
≠BUSINESS OUTCOME?
Did the intended business
result actually happen?
A successful API call is not the same thing as achieving the result the user intended.
07ONE PURPOSE
One Purpose.
Multiple Business
Interactions.
A single human purpose may span multiple businesses, systems, and interactions.
ABIS explores how those interactions and their outcomes can be understood across system boundaries.
One human purpose can span multiple businesses, systems, and interactions—from travel and lodging to payments, dining, purchases, and administrative steps—before a single business outcome can be evaluated.
Company and service names are examples only. They do not indicate partnership or ABIS compatibility.
08PROTOCOL NEUTRAL
ABIS DOES NOT REPLACE AGENT PROTOCOLS.
Protocol Neutral.
AI AGENTS
MCPA2AUCPAPIsOther systems
Business Interactions / Business Outcomes
Different environments.
A shared business concern.
Existing protocols help agents connect, communicate, discover capabilities, and execute actions.
ABIS focuses on the business interaction and business outcome across those environments.
ABIS is complementary.
09PUBLIC v0.1
Public v0.1
01Concept & Architecture Release
PUBLICNON-NORMATIVEOPEN FOR REVIEW
ABIS v0.1 introduces the public concept, terminology, scope, architecture, examples, governance, and roadmap.
It is an early public release intended for discussion, validation, and ecosystem feedback.
Interactive Demonstrator
A non-normative demo across five business cases showing Business Interaction and Business Outcome.
Try the DemonstratorDeveloper Previewv0.1.0
ABIS Reference Runtime v0.1.0
A Developer Preview demonstrating Business Interaction execution, persistent reference business state, Native Business Result handling, idempotency, and execution trace.
Run the Reference Runtime10ROADMAP
From Concept
to Adoption.
- 01
Public concept
- 02
Industry validation
- 03
Multi-company PoC
- 04
Interoperability validation
- 05
Specification evolution
- 06
De facto adoption
LONG-TERM VISION
Global Validation → International Standardization
An intended direction, not a guaranteed outcome.
Business Interaction／Business Outcome
WHO WE VALIDATE WITH
Organizations we hope to
validate with
- 01
Companies building or operating AI services
- 02
Reservation, commerce, travel, mobility, and payment platforms
- 03
Business systems and SaaS providers
- 04
System integrators and implementation partners
- 05
Enterprises and public-sector organizations
- 06
Universities, research institutions, and technical communities
WHAT WE VALIDATE
What we want to validate together
- 01
Test in real use cases
Use Case Validation
- 02
Run multi-company scenarios
Multi-company PoC
- 03
Test across companies and systems
Interoperability Testing
- 04
Review the public specification
Specification Review
- 05
Collect technical feedback
Technical Feedback
- Participate
Organizations join
- Validate
Test in real environments
- Improve
Refine the specification
- Adopt
Toward shared adoption
VALIDATE TOGETHER
Join ABIS validation
with your
organization.
Contact Us About Validation(Opens in a new tab)
PoC, technical review, and use-case discussions are welcome,
even if you are still in the early evaluation stage.
11BEYOND ZERO CLICK
Beyond Zero Click.
From technical execution to business outcome.