Skip to main content

​
Anonymous public profile access

Search published organization names, read individual summaries or batch named profiles without an account, key, token or payment. REST, the Public Profiles MCP, NLWeb, A2A, SDKs and the CLI use bounded public summaries with canonical citations. The fictional sandbox never queries production records. The hosted Public Profiles MCP includes search, single reads and a batch of one to five named profiles. MCP Apps-compatible hosts can show an optional profile explorer with filters, comparisons and canonical citations; ordinary clients retain text and structured results. REST supports both /api/v1/public/batch and the original /api/v1/public/profile-batch. Run the walkthrough · Public reader OpenAPI and permissions · Developer reference and SDKs · Versioning and deprecation policy

​
Intelligence and task access

Paid-task availability: Reviewed bounded request. Execution: Manual / scoped. Automated paid-task invocation: Not currently available. Paid-task API endpoint: None. Paid-task MCP execution: None. Anonymous public profile readers are available separately; see the developer reference.
  • Start with the overall Altss public index and agent instructions linked below.
  • Read public canonical pages and Markdown representations; prefer the most specific entity URL when citing.
  • Choose an existing task and prepare its required inputs. A human reviews purpose, scope, sources and price before work.
  • Check evidence, unknowns and rights before using the result.
Altss public llms.txt · Agent instructions

​
Altss Documentation MCP

The Altss Documentation MCP is documentation-scoped. It provides search and a read-only virtual documentation filesystem. Mintlify also exposes submit_feedback, a write action that sends documentation feedback to Mintlify analytics. Never submit credentials, private records or customer context. It does not grant intelligence queries, premium records, database access or task execution. No Altss intelligence MCP is currently offered. Inspect the published MCP Registry record for its endpoint and metadata.