# Altss public reading and account access

Public website documents, Markdown, descriptive catalogs and schemas require no account, API key or OAuth token. Fetch their published URLs with ordinary HTTP GET and follow canonical links.

## Discover the public reader

Read the [focused public reader OpenAPI](https://altss.com/api/v1/public/openapi.json) for search, individual summaries and the batch operation. Its production and fictional sandbox servers share the same response contract. The [API directory](https://altss.com/api/v1) and OpenAPI x-altss-access object declare authentication: none, registrationRequired: false, credentialsAccepted: false, an empty oauthScopes list and the exact permitted operation IDs. These are anonymous access descriptions, not OAuth scopes.

## Pick an access method

Use ordinary HTTP for REST, Markdown and catalogs, or connect an MCP client to https://altss.com/mcp. Both public readers work without registration, identity claims, credential exchange or an access token. There is no public key-generation step. Paid Console access follows the separate application's sign-in and agreed entitlements.

## Try an anonymous public read

1. Discover the [public API directory](https://altss.com/api/v1) and its [OpenAPI contract](https://altss.com/api/v1/openapi.json). Public reading needs no registration or token exchange.
2. Try the [fictional sandbox](https://altss.com/api/v1/sandbox) first. Its examples never query production records; example.com URLs are fixture citations, not real companies.

```bash
curl --fail-with-body --silent --show-error "https://altss.com/api/v1/sandbox/public/profiles?query=Example&limit=2"
```

3. To exercise a batch, POST one to 5 unique slugs. This example intentionally includes one missing fixture: expect per-item statuses 200 and 404.

```bash
curl --fail-with-body --silent --show-error \
  --header 'Content-Type: application/json' \
  --data '{"slugs":["example-capital-01","missing"]}' \
  "https://altss.com/api/v1/sandbox/public/profile-batch"
```

4. For an actual public organization, use https://altss.com/api/v1/public/profile-batch with its explicit public slugs, or use the individual search/read operations. Cite returned canonical URLs. Never send application cookies, passwords or customer data to these public interfaces.

## Public read errors and retries

For REST, 400 means invalid input, 403 means an unapproved host or browser Origin, and 404 means a profile was not found. A 429 includes Retry-After; honor it. A 503 is a temporary data failure, not an empty successful record. An HTTP 200 batch can contain per-item 404 or 503 outcomes; inspect every item and retry temporary failures with backoff. See the OpenAPI operation for the full response contract.

## Versioning and deprecation policy

The [public API policy](https://altss.com/api-policy.md) explains URL major versions, compatibility, migration notices, the Deprecation header (RFC 9745) and the Sunset header (RFC 8594). No public endpoint is currently deprecated or scheduled for withdrawal. These headers will describe actual announced changes; clients should not expect a fabricated retirement date.

## Find public information

### Find and cite public profiles

Connect Altss Public Profiles at https://altss.com/mcp for bounded name search, individual reads and batches of up to five profiles with canonical citations. REST, NLWeb and A2A public readers are also documented in the developer reference. No account or token is needed. These services expose limited published summaries, not private contacts or customer records.

- [Public-profile MCP connection and limits](https://altss.com/developers)
- [Public-profile MCP server card](https://altss.com/.well-known/mcp/public-server-card.json)
- [Public A2A reader card](https://altss.com/.well-known/agent-card.json)
- [Public REST specification](https://altss.com/openapi.json)
- [Public directory](https://altss.com/profile/directory)

### Understand Altss

Altss provides private-markets intelligence for investment, fundraising and institutional business development. Research organizations, people, funds and companies with ownership, commitment, transaction and relationship context. Intelligence provides research; Capital adds Fundraising OS workflows. Revenue and Agents accept scoped, manually reviewed requests.

- [Platform](https://altss.com/platform)

### Compare published plans

Read current prices, eligibility, access scope and commercial terms before starting an order or configuration request.

- [Pricing](https://altss.com/pricing)
- [Commercial catalog](https://altss.com/commercial-catalog.json)

### Check coverage

Read each published population's definition and measurement date. An aggregate count does not establish verification of every record.

- [Coverage](https://altss.com/coverage)
- [Data documentation](https://docs.altss.com/data)

### Check evidence and dates

Altss combines independently collected public-source business information, Altss-developed research and derived analysis, and commercially licensed contact enrichment. Public facts carry source references, collection dates and relevant evidence; known source restrictions remain applicable. Licensed enrichment follows recorded provider or dataset permissions for the intended use and delivery. Collection method, factual verification, privacy duties and redistribution rights are separate questions. Page modified records a page-content change; source captured records retrieval; fact observed records when evidence was observed; entity verified records a recheck; aggregate measured records a population measurement. These dates are not interchangeable. An absent verification date means unknown.

- [Methodology](https://altss.com/methodology)
- [Evidence documentation](https://docs.altss.com/results/evidence)

### Understand access

Standard subscription intelligence is used in-platform. No public raw-data API, CSV export or bulk download of Altss content, data feed or graph-replication access is offered; customers can export their own data. Public factual pages and their Markdown equivalents may be read and cited. Agents accepts scoped requests for bounded paid results through manual commercial review; no automated external task transport is live.

- [Access and rights](https://docs.altss.com/access-and-rights)

### Find public resources

Start with the machine index, follow advertised Markdown alternates and cite canonical HTML URLs. Public reading requires no account or API key.

- [Developer reference](https://altss.com/developers)
- [Machine index](https://altss.com/llms.txt)
- [Agent guidance](https://altss.com/agents.md)
- [Public reading skill](https://altss.com/skills/altss-public-research/SKILL.md)
- [Profile verification skill](https://altss.com/skills/altss-profile-verification/SKILL.md)
- [Listing preparation skill](https://altss.com/skills/altss-listing-preparation/SKILL.md)
- [Official public-profile MCP registry record](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.altss-data%2Fpublic-profiles/versions/1.1.0)
- [Official documentation MCP registry record](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.altss-data%2Fdocs/versions/1.0.0)
- [Documentation MCP on Glama](https://glama.ai/mcp/connectors/io.github.altss-data/docs)

## Approved account access

Use the [Altss application](https://app.altss.com/login) for existing approved-account access. Follow the application's actual sign-in flow. Never put passwords or tokens in a public URL, a research prompt or this website's forms.

The existing account issuer is https://auth.altss.com/ . Its [OpenID Connect discovery](https://auth.altss.com/.well-known/openid-configuration) and [OAuth authorization-server metadata](https://auth.altss.com/.well-known/oauth-authorization-server) describe that sign-in service. Use only an approved application client and its configured permissions. These documents do not grant access to the public reader or establish a Console API audience, machine client, agent registration flow or paid entitlement.

The forthcoming agent-to-agent Console will publish its actual API/MCP resource URLs, issuer binding, supported scopes and onboarding instructions when that service is deployed. Until then, this website advertises the working anonymous public interfaces only; account tokens must not be sent to them.
Standard subscription intelligence is used in-platform. No public raw-data API, CSV export or bulk download of Altss content, data feed or graph-replication access is offered; customers can export their own data. Public factual pages and their Markdown equivalents may be read and cited. Agents accepts scoped requests for bounded paid results through manual commercial review; no automated external task transport is live.

## Agent integration boundaries

Where the browser supports the experimental WebMCP draft, the homepage and /ai offer get_altss_public_guide. It returns the published summaries and links below. It reads no form values, makes no network requests and changes no account or purchase state. Other browsers can use these links and Markdown directly.
The [Altss Documentation MCP](https://docs.altss.com/mcp) supports documentation search and filesystem reads; submit_feedback writes documentation feedback to Mintlify analytics. The [documentation MCP discovery document](https://docs.altss.com/.well-known/mcp) belongs to the documentation provider. Check its advertised transport and actual authentication requirements. It grants no Altss application access, premium records or task execution.
The [public-profile MCP](https://altss.com/mcp) uses anonymous Streamable HTTP POST and needs no credentials. It supports bounded name search, individual reads and batches of up to five profiles with canonical citations; see [connection details and limits](https://altss.com/developers). It never forwards application cookies or tokens. Public access does not grant private entitlements.
This MCP reads published public pages only. It cannot sign in to the Console, read paid or tenant-private records, retrieve contact enrichment, or perform account operations. Registration, credential exchange and token revocation do not apply to this anonymous reader.
Public REST /api/v1/public profile reads, NLWeb POST /ask and A2A 1.0 POST /a2a are also anonymous and read-only. See [exact requests and limits](https://altss.com/developers) and the [public A2A card](https://altss.com/.well-known/agent-card.json). They do not accept application credentials or grant private entitlements.
The [public API sandbox](https://altss.com/api/v1/sandbox/public/profiles?query=Example&limit=2) reads fictional fixtures with separate instance budgets and replay caches; it never queries production records. The [Python, JavaScript and Go clients and CLI](https://github.com/Altssdata/public-client) read public documents and bounded published profile summaries. The JavaScript client and CLI are published as [altss-public-client on npm](https://www.npmjs.com/package/altss-public-client); the Python client is published as [altss-public-client on PyPI](https://pypi.org/project/altss-public-client/); the [Go module documentation and versions](https://pkg.go.dev/github.com/Altssdata/public-client/go) are on Go Packages. Use each language's version shown in the developer reference. Their sandbox options affect profile methods only.
The read-only batch is POST https://altss.com/api/v1/public/profile-batch (also available at /api/v1/public/batch) with Content-Type: application/json and a body such as {"slugs":["daimler-truck-ag"]}. The [OpenAPI operation readPublicProfileBatch](https://altss.com/openapi.json) defines its request and response. Supply one to five unique public slugs and inspect each result's status; an HTTP 200 does not mean every profile was found. This is a bounded public-page read, not bulk access to the paid dataset.
No public intelligence OAuth issuer, API-key provisioning endpoint, protected-resource metadata or private intelligence MCP server is advertised. This document is guidance, not OAuth metadata or permission to bypass sign-in.
