---
title: "A2A and agent discovery."
description: "Altss’s anonymous website A2A reader and protected paid Console are separate services. Discover the interface, skills and authorization on the server you intend to use."
canonical: "https://altss.com/console/docs/a2a"
last-updated: "2026-11-17"
---

# A2A and agent discovery.

Altss’s anonymous website A2A reader and protected paid Console are separate services. Discover the interface, skills and authorization on the server you intend to use.

Last modified: 2026-11-17

## Choose a service before a protocol

The public website exposes a bounded A2A reader for published Altss information. Its Agent Card describes the supported tasks and interface. That reader is useful for public research discovery, but it does not grant a machine credential, fund a Console wallet or execute a paid financial-research request. Start by deciding whether the job needs public reading or an available paid Console result.

## Public A2A discovery

- [Website Agent Card](https://altss.com/.well-known/agent-card.json): The advertised public-reader interfaces and supported skills.
- [Public reader documentation](https://altss.com/developers): Anonymous profile search, reading and supported agent interfaces.
- [Public machine API index](https://altss.com/openapi.json)

## Protected Console integration

Use the currently published Console REST and MCP contracts for paid research. A website Agent Card is not evidence that the protected Console accepts the same protocol or methods. Before using another paid interface, require its own current server discovery, capability definition, authentication contract and purchase flow. Do not send Console credentials to the public reader or infer an endpoint from its name.

## What an agent should verify

| Discovery item | Why it matters |
| --- | --- |
| Service URL | Keeps public reading and paid execution on the intended host |
| Protocol and version | Determines the supported wire contract rather than relying on a product label |
| Advertised skills | Limits requests to operations actually described by that service |
| Authentication | Distinguishes anonymous reading from organization-scoped access |
| Purchase authority | Separates credential approval from acceptance of a paid action |
| Result and error handling | Preserves evidence and financial state across an agent handoff |


## Composition without assumptions

A customer-controlled agent workflow can read published context, resolve an issuer identifier and then obtain a quote through a supported Console interface. Pass the explicit entity and evidence to the next step; retain the Console quote and receipt separately from public-reader output. The workflow’s orchestration does not expand the individual services’ permissions or supported operations.

## Connect paid research

- [Console REST contract](https://altss.com/console/docs/api)
- [Console MCP contract](https://altss.com/console/docs/mcp)
- [Multi-agent execution design](https://altss.com/console/agent-execution#multi-agent-workflows)
- [Read the current Console catalog](https://console.altss.com/tools.json): Executable tools, input schemas and the current commercial offer.

[Inspect the public Agent Card](https://altss.com/.well-known/agent-card.json)

[Explore capabilities](https://altss.com/console/capabilities)

## Connect with the contract in view.

Start with the capability, its evidence requirements and the decision your team needs to make. Confirm the available tool and permitted use before execution.

[Read the connection guide](https://console.altss.com/connect)

[Discuss a requirement](https://altss.com/contact)

Canonical URL: https://altss.com/console/docs/a2a

