A2A Card Types. Structured Information for Companies, Products, Capabilities, Agents and RFQs
Direct RFQ uses five connected card types to describe the principal objects involved in modern B2B commerce.
Each card answers a different commercial question:
- Who is the supplier?
- What product is available?
- What can the supplier perform?
- What can an AI agent do?
- What does the buyer need?
Together, the cards create a structured information architecture for:
- AI search;
- answer engines;
- supplier discovery;
- product discovery;
- technical qualification;
- commercial comparison;
- procurement systems;
- requests for quotation;
- buyer agents;
- supplier agents;
- agentic commerce.
The Direct RFQ card architecture includes:
- A2A Product Card;
- A2A Business Card;
- A2A Capability Card;
- A2A Agent Card;
- Direct RFQ Card.
A company does not need to implement all five card types at the beginning.
A practical project can start with one company, one product or one recurring purchasing requirement and expand gradually as the information model becomes established.
Primary CTA: Choose Your Card Type
Secondary CTA: Explore the A2A Card Framework
One Framework, Five Business Objects
B2B commerce is built around several different entities.
A company is not the same as its product.
A product is not the same as the production capability behind it.
A company’s AI agent is not the same as the company itself.
A purchasing requirement is not the same as the supplier’s commercial offer.
When these elements are mixed together on one general web page, both people and AI systems may struggle to understand:
- who is responsible for the offer;
- which product is being described;
- which capabilities are available;
- which data is current;
- what the buyer is requesting;
- what action can be performed next.
The Direct RFQ card architecture separates these objects while connecting them through stable relationships.
For example:
- the A2A Business Card identifies the supplier;
- the A2A Product Card describes a product offered by that supplier;
- the A2A Capability Card explains the operational capability supporting the offer;
- the A2A Agent Card describes a functioning agent operated by the company;
- the Direct RFQ Card describes the buyer’s specific requirement.
This creates a structured relationship between supply, demand, information and action.
Overview of the Card Types
| Card type | Main subject | Primary question |
|---|---|---|
| A2A Product Card | Product, model or configuration | What can the buyer purchase? |
| A2A Business Card | Company or legal business entity | Who is the supplier? |
| A2A Capability Card | Production, service or operational capability | What can the supplier actually deliver? |
| A2A Agent Card | Functioning AI agent | What can the agent do and how can it be engaged? |
| Direct RFQ Card | Specific purchasing requirement | What does the buyer need? |
Each card can exist as:
- a complete human-readable web page;
- a structured content template;
- a machine-readable data object;
- a public JSON resource;
- a feed item;
- an API response;
- part of an agent-assisted workflow.
The visible page should remain understandable and useful for human readers.
Machine-readable formats should reflect the same verified information.
A2A Product Card
Describe a Product in a Form That Can Be Found, Compared and Qualified
An A2A Product Card describes a specific B2B product, model, variant or commercial configuration.
It provides more than a marketing description.
It combines:
- product identity;
- technical specifications;
- applications;
- operating limits;
- compatibility;
- variants;
- pricing information;
- availability;
- delivery;
- documentation;
- qualification rules;
- Direct RFQ actions.
The Product Card should help a buyer or AI agent determine:
- what the product is;
- who manufactures it;
- who supplies it;
- which model or version is relevant;
- whether it fits the intended application;
- which technical data is still required;
- how the price is determined;
- whether the product is currently available;
- how to request a complete quotation.
Typical Product Card Fields
An A2A Product Card may include:
- product name;
- manufacturer;
- brand;
- model;
- SKU or product code;
- category;
- version;
- lifecycle status;
- intended use;
- technical parameters;
- units;
- supported dimensions;
- performance;
- operating conditions;
- limitations;
- optional equipment;
- compatible systems;
- price or pricing method;
- price validity;
- currency;
- MOQ;
- stock status;
- lead time;
- delivery area;
- installation;
- commissioning;
- training;
- warranty;
- service;
- spare parts;
- datasheets;
- declarations;
- certificates;
- RFQ fields.
When to Use a Product Card
Use an A2A Product Card when the main subject is:
- an individual industrial product;
- a machine;
- a component;
- a material;
- a consumable;
- a product variant;
- a product configuration;
- a commercially available solution.
Main Benefit
The Product Card transforms a conventional product page into a structured, comparable and qualification-ready business asset.
CTA: Explore the A2A Product Card
A2A Business Card
Describe the Company Behind the Offer
An A2A Business Card describes a legal business entity and its commercial role.
It helps buyers, procurement systems and AI agents determine:
- who the company is;
- where it operates;
- whether it is a manufacturer, distributor or service provider;
- which industries and markets it serves;
- which certifications and authorisations it holds;
- which products and capabilities it provides;
- how the company can be contacted and qualified.
A traditional About page often focuses on history, mission and brand narrative.
An A2A Business Card adds the structured information required for supplier discovery and verification.
Typical Business Card Fields
An A2A Business Card may include:
- legal company name;
- trading names;
- legal form;
- registration number;
- tax identifier;
- headquarters;
- operational locations;
- year established;
- ownership relationships;
- company roles;
- industries served;
- markets served;
- countries covered;
- languages;
- brands;
- manufacturers represented;
- products;
- services;
- production capabilities;
- warehouse capabilities;
- delivery coverage;
- installation coverage;
- technical service;
- certifications;
- authorisations;
- trademarks;
- memberships;
- contact points;
- enquiry routing;
- data owner;
- verification status.
When to Use a Business Card
Use an A2A Business Card when the main subject is:
- a manufacturer;
- a distributor;
- a wholesaler;
- an importer;
- a system integrator;
- a contract manufacturer;
- an industrial service provider;
- a rental company;
- a software provider;
- an AI agent operator.
Main Benefit
The Business Card makes the company’s legal identity, commercial role, trust signals and operational scope explicit.
CTA: Explore the A2A Business Card
A2A Capability Card
Describe What the Supplier Can Actually Perform
An A2A Capability Card describes a specific production, service, engineering, logistics or operational capability.
It is particularly useful when the buyer is not searching for a fixed catalogue product.
The buyer may instead need a company that can:
- manufacture a custom component;
- process a specific material;
- integrate a production line;
- install equipment;
- perform maintenance;
- test a product;
- fulfil orders;
- provide contract packaging;
- support a technical process.
A general statement such as “we provide customised solutions” does not provide enough information for reliable supplier matching.
The Capability Card defines the real scope, conditions and limitations of the supplier’s ability.
Typical Capability Card Fields
An A2A Capability Card may include:
- capability name;
- capability category;
- process description;
- accepted inputs;
- expected outputs;
- technology;
- machinery;
- tools;
- supported materials;
- dimensions;
- tolerances;
- performance range;
- production capacity;
- minimum batch;
- maximum volume;
- minimum project size;
- quality procedures;
- certifications;
- required drawings;
- required technical files;
- sample requirements;
- tooling requirements;
- validation process;
- lead-time determinants;
- geographic coverage;
- service availability;
- exclusions;
- RFQ requirements.
When to Use a Capability Card
Use an A2A Capability Card when the main subject is:
- contract manufacturing;
- production capacity;
- machining;
- converting;
- processing;
- packaging;
- engineering;
- integration;
- installation;
- maintenance;
- logistics;
- warehousing;
- fulfilment;
- custom software or automation;
- specialist B2B services.
Main Benefit
The Capability Card helps buyer agents and procurement teams match a purchasing requirement with a supplier’s real operational ability.
CTA: Explore the A2A Capability Card
A2A Agent Card
Describe a Functioning Agent and Its Operational Authority
An A2A Agent Card describes a functioning AI agent and the conditions under which other agents, users or systems can interact with it.
It may contain technical discovery information as well as business context.
The technical layer may describe:
- agent name;
- description;
- protocol support;
- endpoint;
- supported interfaces;
- declared skills;
- communication methods;
- authentication requirements;
- security schemes.
The business layer may additionally explain:
- the legal organisation operating the agent;
- the agent’s business purpose;
- supported industries;
- supported markets;
- permitted actions;
- prohibited actions;
- transaction limits;
- human approval requirements;
- escalation procedures;
- audit and logging rules;
- data access conditions.
Important Terminology
The Direct RFQ card framework uses A2A Card as an umbrella term for several structured business information objects.
However, the official Agent2Agent Agent Card is a specific technical discovery object for a functioning AI agent.
An A2A Product Card, Business Card or Capability Card should not be presented as an official protocol Agent Card.
The objects can complement one another.
For example:
- the Business Card identifies the company operating the agent;
- the Product Card describes products available through the agent;
- the Capability Card describes services the agent can help qualify;
- the official Agent Card describes how another system communicates with the agent.
Typical Agent Card Fields
An A2A Agent Card may include:
- agent name;
- agent identifier;
- legal operator;
- description;
- supported protocol version;
- endpoint;
- supported content types;
- declared skills;
- authentication;
- security requirements;
- supported markets;
- supported languages;
- allowed actions;
- transaction limits;
- approval rules;
- escalation contact;
- data policy;
- logging policy;
- version;
- status.
When to Use an Agent Card
Use an A2A Agent Card when the company operates a real digital agent that can:
- answer product questions;
- qualify requirements;
- provide approved documents;
- prepare RFQs;
- support quotation preparation;
- check authorised data;
- route enquiries;
- initiate approved actions.
Main Benefit
The Agent Card makes the agent’s capabilities, authority and interaction rules explicit.
CTA: Explore the A2A Agent Card
Direct RFQ Card
Describe What the Buyer Needs
A Direct RFQ Card represents a specific purchasing requirement.
It structures the technical, commercial, logistical and documentary information a supplier needs before preparing a reliable quotation.
Many traditional RFQs are incomplete.
They may omit:
- dimensions;
- materials;
- operating conditions;
- quantities;
- delivery location;
- required date;
- installation requirements;
- documentation;
- response format;
- decision criteria.
This creates repeated clarification and non-comparable supplier responses.
The Direct RFQ Card creates a more complete and consistent request.
Typical Direct RFQ Card Fields
A Direct RFQ Card may include:
- RFQ title;
- RFQ identifier;
- buyer identity;
- request status;
- publication date;
- response deadline;
- confidentiality level;
- product or capability requested;
- intended application;
- technical requirements;
- dimensions;
- materials;
- operating conditions;
- quantity;
- unit;
- forecast demand;
- acceptable alternatives;
- mandatory conditions;
- delivery location;
- required delivery date;
- Incoterms;
- payment expectations;
- required documentation;
- installation;
- commissioning;
- training;
- warranty;
- supplier qualification conditions;
- quotation response fields;
- evaluation criteria;
- responsible contact.
When to Use a Direct RFQ Card
Use a Direct RFQ Card when the main subject is:
- a specific request for quotation;
- a recurring purchasing requirement;
- a sourcing event;
- a supplier discovery request;
- a technical procurement need;
- a capability sourcing requirement;
- a public or restricted buyer request.
Main Benefit
The Direct RFQ Card helps buyers submit more complete requirements and helps suppliers respond using a more comparable structure.
CTA: Explore the Direct RFQ Card
How the Cards Work Together
The five card types are designed to form a connected information system.
Example Relationship
A buyer needs an automatic pallet wrapping system.
The card architecture may connect:
A2A Business Card
Identifies the supplier, its legal entity, territory, service coverage and manufacturer relationships.
A2A Product Card
Describes a specific pallet wrapping machine, including technical parameters, options, price rules, availability and warranty.
A2A Capability Card
Describes the supplier’s ability to perform site assessment, installation, commissioning, training and technical service.
A2A Agent Card
Describes the supplier’s AI agent, which can collect pallet dimensions, load weight, film type, throughput and delivery location.
Direct RFQ Card
Contains the buyer’s specific requirement, quantity, operating conditions, required delivery date and requested scope.
The cards answer different questions but share common identifiers and relationships.
Card Relationships
A card can reference other cards.
Typical relationships include:
- company offers product;
- company provides capability;
- product is manufactured by company;
- product is distributed by company;
- capability supports product;
- agent is operated by company;
- agent provides information about product;
- agent supports capability qualification;
- RFQ requests product;
- RFQ requests capability;
- RFQ is submitted to company;
- product is a possible response to RFQ.
These relationships help people and AI systems reconstruct the commercial context without relying on assumptions.
Which Card Type Do You Need?
Choose an A2A Product Card when:
- you want to prepare a specific product for AI search and buyer qualification;
- your product page lacks complete technical or commercial data;
- buyers repeatedly ask the same preliminary questions;
- different variants are difficult to distinguish;
- you want to create a structured RFQ path for one product.
Choose an A2A Business Card when:
- your company role is unclear online;
- buyers need to verify your legal identity;
- you operate as both distributor and service provider;
- you represent several brands;
- you want to publish a structured supplier profile.
Choose an A2A Capability Card when:
- you sell custom production or services;
- buyers search for an outcome rather than a named product;
- your capacity and technical limits are not clearly described;
- you want to improve supplier matching;
- your offer depends on technical files, samples or project qualification.
Choose an A2A Agent Card when:
- your company operates a functioning AI agent;
- external systems need to discover the agent;
- the agent has defined skills and endpoints;
- permitted actions and transaction limits must be stated;
- human approval and escalation rules need to be explicit.
Choose a Direct RFQ Card when:
- you want to publish a specific purchasing requirement;
- your procurement team receives inconsistent supplier responses;
- enquiries repeatedly lack important technical data;
- supplier comparison is difficult;
- you want a reusable RFQ structure.
Start with One Primary Card
A company does not need to create every card at once.
The most effective starting point often depends on the business model.
Product-Led Company
Start with:
- A2A Business Card;
- A2A Product Card;
- Direct RFQ section.
Contract Manufacturer
Start with:
- A2A Business Card;
- A2A Capability Card;
- Direct RFQ Card.
Distributor
Start with:
- A2A Business Card;
- flagship A2A Product Cards;
- availability and commercial fields;
- structured RFQ workflow.
Procurement Organisation
Start with:
- Direct RFQ Card;
- supplier response structure;
- supplier qualification criteria.
AI Agent Operator
Start with:
- A2A Business Card;
- official A2A Agent Card;
- related Product or Capability Cards;
- action and governance rules.
Common Information Layers
Although each card type serves a different purpose, all cards use a common information architecture.
Identity
What is the object?
Who owns or provides it?
How is it identified?
Description
What does the object represent?
What is its purpose?
Qualification
Under which conditions is it relevant or suitable?
Commercial Information
What pricing, availability, delivery or service conditions apply?
Evidence
Which sources, documents or records support the information?
Actions
What can a buyer, supplier or agent do next?
Governance
Who controls the data, how long is it valid and which permissions apply?
This shared structure makes the cards easier to connect, compare, maintain and reuse.
Human-Readable and Machine-Readable Cards
Every card should begin as a complete, useful web page.
The page should be understandable to:
- buyers;
- engineers;
- procurement teams;
- sales teams;
- service teams;
- business partners.
Depending on the implementation, the same card may also be represented through:
- structured HTML;
- schema markup;
- JSON-LD;
- public JSON files;
- product feeds;
- RFQ feeds;
- APIs;
- authenticated resources;
- agent endpoints.
The machine-readable version should remain consistent with the visible page.
Time-sensitive information should include:
- a last-updated date;
- validity period;
- status;
- responsible owner.
Card Identification and Versioning
Every published card should have a stable identity.
Recommended fields include:
- card ID;
- card type;
- version;
- status;
- publication date;
- last update;
- data owner;
- verification status;
- canonical URL;
- language;
- market scope.
Suggested Card Statuses
Cards may use statuses such as:
- Draft;
- Published;
- Verified;
- Company Confirmed;
- Commercially Current;
- Indicative;
- Subject to Confirmation;
- Update Required;
- Archived;
- Demonstration;
- Public Information Only.
Why Versioning Matters
Business information changes.
A product price may be updated.
A model may be discontinued.
A company may gain a new certification.
A production capability may increase.
An RFQ deadline may be extended.
Versioning helps people and systems determine which information is current and what has changed.
Card Verification
A card should clearly state how the information was prepared.
Possible verification levels include:
Public Information Only
The card was prepared from publicly available sources and has not been confirmed by the represented company.
Company Confirmed
The company reviewed and confirmed the content.
Technically Verified
Relevant technical data was reviewed by a responsible technical party.
Commercially Current
Time-sensitive commercial information was confirmed for the stated validity period.
Demonstration
The card illustrates the structure and should not be treated as an active commercial offer.
Verification status helps prevent a public example from being interpreted as a binding or current offer.
Card Types and FUCTEG
Each card type can be evaluated using the FUCTEG framework.
Findable
Can the correct card, entity, product, capability, agent or RFQ be located?
Understandable
Can the subject, fields, units and relationships be interpreted correctly?
Comparable
Does the card contain the attributes required for meaningful evaluation?
Trustworthy
Can important claims be traced to responsible sources and current evidence?
Executable
Does the card provide a defined next action?
Governable
Are ownership, validity, permissions and limitations clear?
The balance between these criteria may vary by card type.
For example:
- Product Cards require strong technical and commercial comparability;
- Business Cards require strong identity and trust data;
- Capability Cards require clear qualification limits;
- Agent Cards require strong action governance;
- Direct RFQ Cards require complete requirement and response fields.
Card Types and the Direct RFQ Standard
The Direct RFQ Standard defines the shared structure, field principles and governance rules used across the card system.
The relationship can be summarised as follows:
- the Direct RFQ Standard defines the methodology;
- A2A Cards are structured information objects;
- A2O Optimization improves the quality and usability of those objects;
- Agentic Commerce Readiness prepares the organisation to use them operationally.
The Card Types section presents the individual objects created within this broader framework.
Card Types and A2O Optimization
A2O, or Agent-to-Agent Optimization, is the process of making business information usable by AI agents.
An A2O project may identify that a company needs:
- a clearer Business Card;
- structured Product Cards;
- Capability Cards for custom services;
- Direct RFQ Cards for recurring enquiries;
- an Agent Card for a functioning supplier agent.
A2O is therefore the optimization process.
The cards are the structured outputs created or improved through that process.
Card Types and Agentic Commerce
Agentic commerce requires structured information about both supply and demand.
The card architecture provides that information.
Supply-Side Cards
- A2A Business Card;
- A2A Product Card;
- A2A Capability Card.
Interaction Card
- A2A Agent Card.
Demand-Side Card
- Direct RFQ Card.
Together, these objects can support a workflow in which:
- a buyer agent identifies a requirement;
- a Direct RFQ Card structures the demand;
- supplier Business, Product and Capability Cards are discovered;
- the agent compares initial suitability;
- missing data is requested;
- the supplier agent prepares or routes the response;
- a human approves the final commercial decision.
Card Type Implementation Process
1. Select the Primary Object
Determine whether the main subject is:
- a company;
- a product;
- a capability;
- an agent;
- an RFQ.
2. Identify Related Objects
Determine which other cards should be connected.
A Product Card usually connects to a Business Card.
A Capability Card usually connects to a supplier.
An Agent Card should identify its operator.
A Direct RFQ Card may reference products, capabilities and potential suppliers.
3. Collect Source Information
Sources may include:
- website pages;
- company records;
- product catalogues;
- datasheets;
- manuals;
- declarations;
- certificates;
- price lists;
- ERP data;
- PIM data;
- internal procedures;
- existing RFQs.
4. Map the Information
Organise the data into:
- Identity;
- Description;
- Qualification;
- Commercial;
- Evidence;
- Action;
- Governance.
5. Identify Gaps
Common gaps include:
- missing identifiers;
- inconsistent names;
- missing units;
- unclear business roles;
- no limitations;
- no price validity;
- missing qualification questions;
- no evidence owner;
- no action path;
- no update responsibility.
6. Prepare the Human-Readable Card
Create a complete web page that is useful for buyers, engineers, sales teams and procurement teams.
7. Prepare the Action or RFQ Layer
Define:
- required inputs;
- optional inputs;
- responsible team;
- response format;
- expected response time;
- approval requirements;
- escalation.
8. Prepare the Machine-Readable Layer
Where appropriate, develop:
- schema markup;
- JSON-LD;
- public JSON;
- feeds;
- APIs;
- agent-accessible resources.
9. Verify and Publish
Confirm:
- factual accuracy;
- technical consistency;
- commercial validity;
- document status;
- ownership;
- permissions;
- update process.
Typical Card Project Deliverables
A Direct RFQ card project may include:
- recommended card type;
- card hierarchy;
- URL structure;
- SEO title;
- meta description;
- focus keyphrase;
- complete page content;
- field map;
- attribute structure;
- technical data structure;
- commercial data structure;
- qualification questions;
- evidence structure;
- Direct RFQ section;
- CTA structure;
- governance fields;
- verification status;
- schema recommendations;
- JSON field recommendations;
- internal linking plan;
- implementation roadmap.
Frequently Asked Questions
What are A2A Card Types?
A2A Card Types are structured information objects used to describe companies, products, capabilities, AI agents and purchasing requirements.
How many card types are included?
The Direct RFQ architecture includes five primary card types:
- A2A Product Card;
- A2A Business Card;
- A2A Capability Card;
- A2A Agent Card;
- Direct RFQ Card.
Does every company need all five card types?
No.
A company can begin with the card that best reflects its immediate business objective.
What is the difference between a Product Card and a Capability Card?
A Product Card describes a specific product or commercial configuration.
A Capability Card describes what a supplier can manufacture, process, integrate or perform.
What is the difference between a Business Card and a Product Card?
The Business Card describes the company behind the offer.
The Product Card describes an individual product supplied by that company.
What is the difference between an Agent Card and a Business Card?
A Business Card describes a legal organisation.
An Agent Card describes a functioning AI agent and its technical and operational capabilities.
Is an A2A Agent Card the same as the other Direct RFQ A2A Cards?
Not exactly.
The official Agent2Agent Agent Card is a technical discovery object for a functioning agent.
Direct RFQ uses A2A Card more broadly as an umbrella term for its business information framework.
The distinction should be stated clearly.
What is the difference between a Direct RFQ Card and a Product Card?
A Product Card represents supply.
A Direct RFQ Card represents demand.
Can the cards be used without an AI agent?
Yes.
The cards can begin as structured human-readable web pages.
AI agents, APIs and feeds can be introduced later.
Can a card exist only as HTML?
Yes.
A complete, crawlable and well-structured HTML page is a valid starting point.
Does every card need a JSON version?
No.
A JSON version can be added when machine-readable reuse provides practical value.
Can one card describe several products?
A catalogue-level card can provide an overview, but materially different products should normally have separate Product Cards.
Can one company have several Capability Cards?
Yes.
Each materially different capability can have its own card.
For example:
- machining;
- assembly;
- contract packaging;
- installation;
- maintenance.
Can a Direct RFQ Card be private?
Yes.
A card can be:
- public;
- restricted;
- invitation-only;
- confidential;
- available through authentication.
Can card information be updated?
Yes.
Every card should have a version, update date and responsible owner.
Are the card types an official international standard?
No.
They are part of the independent Direct RFQ business information framework.
Can the cards support multiple languages?
Yes.
Language versions should use the same identifiers, structure, units, status and commercial scope.
Which card should be created first?
For most suppliers, the best starting point is:
- an A2A Business Card;
- one flagship A2A Product Card or Capability Card;
- a Direct RFQ section.
Choose the Card That Matches Your Business Objective
Structure the Right Object Before Building the Workflow
The effectiveness of an AI-ready B2B information system depends on correctly identifying what is being described.
A company profile should not be used as a product specification.
A product page should not be used as a capability statement.
A capability statement should not be confused with a buyer’s requirement.
An official Agent Card should describe a real functioning agent.
The Direct RFQ card architecture creates clear boundaries between these objects while allowing them to work together.
Choose the card type that best represents your current business objective and build a repeatable model that can later be expanded across products, capabilities, markets and agentic workflows.
Primary CTA: Choose Your Card Type
Secondary CTA: Start with an A2A Business Card
Additional CTA: Request a Card Architecture Review