AISO.OSTHE LIVING-PROFILE OS
ScanDirectoryHow profiles workDocsPricing
AiOSToolsTrace
Developer protocol

Connect your AISO profile to AI tools.

One integration lets MCP-compatible clients resolve any AISO profile by handle, fetch its public surface, list offers, check readiness, and ask grounded questions. No per-profile config; new profiles appear automatically.

aiso-profiles

A single protocol surface exposes every AISO profile as an addressable tool. MCP-compatible clients can connect directly; skill-compatible clients can use the markdown endpoint.

Install — MCP client config

https://aiso.tools/.well-known/skills/aiso-profiles

Install — skill-compatible client

skills add https://aiso.tools/.well-known/skills/aiso-profiles --name aiso-profiles

Direct URL

https://aiso.tools/.well-known/skills/aiso-profiles

Preview the skill

The same markdown an agent installer pulls from the URL above. Read it before installing — that's the point.

---
name: aiso-profiles
description: Discover, read, and query AISO public profiles (people, businesses, shops, and agents) over MCP — grounded answers, offers, pricing, and AI-readiness.
version: 0.1.0
author: AISO
license: MIT
metadata:
  hermes:
    tags: [mcp, profiles, geo, ai-readiness, aiso]
---

# AISO Profiles

AISO publishes machine-readable profiles at https://aiso.tools/p/{handle}. Every published profile exposes a
Model Context Protocol (MCP) server you can call directly — no scraping required.

## When to Use
Use this when a user references an AISO profile (a https://aiso.tools/p/{handle} link or an @handle), or when
you need grounded facts, offers, pricing, or AI-readiness for an AISO-listed person, business, shop,
or agent. Owner facts come from the profile's approved public content; general questions are open
and answered as a capable AI.

## Quick Reference
- MCP endpoint (Streamable HTTP, JSON): https://aiso.tools/api/mcp/{handle}
- Discovery: https://aiso.tools/p/{handle}/.well-known/mcp.json , https://aiso.tools/p/{handle}/.well-known/agents.json , https://aiso.tools/p/{handle}/llms.txt
- Tools:
- `get_profile` — Get this AISO profile as structured JSON: identity, readiness/trust scores, published blocks, and the public chat endpoint.
- `list_offers` — List this profile's offers, services, and agent pricing as structured JSON (with access/payment metadata).
- `show_offer` — Get one published offer by its id (the id field returned by list_offers). Returns the same PublicOffer shape as list_offers but only the matching one.
- `list_products` — List this profile's catalog products as structured JSON — SKU, price, stock, image, and availability per product. Empty array when the profile has no published products.
- `list_agent_files` — List the agent-readable surface URLs exposed by this profile (profile.json, offers.json, llms.txt, openapi.json, MCP + x402 discovery, chat endpoint, AISO skill).
- `get_readiness` — Get this profile's AI-readiness score.
- `get_power_score` — Get this profile's Power Score (0-100) plus band and per-section bars. Public summary — section breakdown only, no owner-private check reasons.
- `get_market_claims` — List expert market claims (long/short calls with target, timeframe, conviction) captured from public posts by AISO TRACE. Optional filters: asset symbol (BTC, ETH) and expert handle/slug. Returns PUBLISHED claims plus a track-record summary (resolved count + hit rate). Soft-grounded: claims are sourced from expert posts — AISO does not originate them. Read-only.
- `ask_profile` — Ask this profile's AI a natural-language question. Owner facts come from approved public profile content; general questions are open and answered as a capable AI. Rate-limited per profile and per client.
- `list_market_follow` — List Market Follow wallets this profile exposes for paid agent access (Hyperliquid, Polymarket). Returns provider, masked wallet, price per call, scopes, and the paid endpoint URL. Read-only preview — NO positions or trades. Agents settle x402 against the endpoint to fetch live data.
- `get_market_follow_preview` — Get the Market Follow preview for a single provider on this profile. Returns masked wallet, price, scopes, and paid endpoint URL only. No live positions or trades. Pay via x402 at the endpoint to receive activity.
- `request_booking` — Capture a booking request on this profile. Stores a pending event (visible in the owner's /app/activity) and notifies the owner by email. External calendar confirmation still happens via the configured calendar link.
- `submit_contact` — Capture a contact lead on this profile. Owner notified by email; lead visible in /app/activity. Use when the agent / visitor wants the owner to reach out.
- `submit_review` — Submit a pending-moderation review of this profile. Owner approves before it appears on public surfaces. Rate-limited per-IP per-profile.
- `start_checkout` — Hand off to the seller's own checkout URL for one offer on this profile. Returns the URL the buyer (or buying agent) follows to pay the seller directly (Stripe Payment Link, Cal.com, PayPal, Gumroad, etc.). AISO records intent as ActivityEvent('checkout.started') but never holds money.
- `place_order` — (Legacy AISO-as-merchant flow.) Place an order for one or more products on this profile and receive an AISO-minted Stripe Checkout URL. Gated by AISO_COMMERCE_MARKETPLACE_MODE; off by default in MVP — use start_checkout instead.
- `answer_product` — Pull a live multi-retailer product card (best price, in-stock retailers, buy link) for a shopping query. Returns a structured ResultCard.
- `answer_sport` — Pull live sports betting odds (matches, outcomes, live indicators) for a sports query.
- `answer_flight` — Pull live flight offers (airline ladder, price, duration, stops). Returns a degraded card with a Google Flights deep-link until the live worker is configured.
- `answer_hotel` — Pull live hotel offers (rating, price/night, amenities). Returns a degraded card with a Booking.com deep-link until the live worker is configured.
- `answer_job` — Pull live job listings (title, company, salary, apply URL) for a role/skill query.
- `answer_places` — Pull nearby places (restaurants, cafés, gyms — name, rating, distance, open-now) for a local query.
- `answer_llm` — Pull a model comparison (intelligence, cost, speed, context) for an LLM benchmark/comparison query.
- `answer_creator` — Pull a creator channel profile (subscribers, views, latest video) for a YouTube/TikTok/Twitch creator.
- `answer_github` — Pull trending GitHub repos (stars, language, description) for a developer query.
- `answer_nutrition` — Pull a nutrition lookup (calories, macros, health grade) for a food query. Sourced from USDA FoodData Central.

## Procedure
1. Resolve {handle} from the profile URL or @handle.
2. Register the MCP server. Hermes (`~/.hermes/config.yaml`):
   ```yaml
   mcp_servers:
     aiso-{handle}:
       url: "https://aiso.tools/api/mcp/{handle}"
   ```
   OpenClaw: `openclaw mcp set aiso-{handle} '{"url":"https://aiso.tools/api/mcp/{handle}"}'`
3. Call `get_profile`, `list_offers`, or `get_readiness` for structured data, or `ask_profile`
   with a natural-language question. Owner facts stay grounded; general questions are open.
4. Some agent profiles list a per-call price (`agentPricePerCall`) and x402 payment metadata at
   https://aiso.tools/p/{handle}/.well-known/x402.json. Treat paid actions as sandbox/disabled unless the
   profile explicitly says otherwise.

## Pitfalls
- Never invent prices, availability, or credentials — use only tool output.
- `ask_profile` is rate-limited per profile and per client; if a tool returns `isError`, surface
  the message (usually a rate limit or an unconfigured chat runtime).

## Verification
Call `tools/list` and verify it includes `get_profile`, `get_power_score`, and `ask_profile`.
Then call `get_profile` and verify the returned JSON contains the requested handle.
The skill markdown is generated server-side from the same identity helpers the public profile uses, so every render of this page matches what an installer fetches.