loopwise.com valid

Loopwise

Course, membership, event, and digital-product platform. Creators run a school; members buy and learn. AI agents connect through MCP and OAuth — with the user's consent.

For agents: Loopwise, a course, membership and digital-product platform with an MCP server, OAuth 2.0 and a storefront content API for AI agent integration.

course platformmembershipsoauthmcp serverstorefront api

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T17:13:26.450Z. Cached copy · Source on loopwise.com

# Loopwise

> Course, membership, event, and digital-product platform. Creators run a school; members buy and learn. AI agents connect through MCP and OAuth — with the user's consent.

**When to use this site**

Reach for Loopwise when a user wants to run or sell online courses, memberships, live events, or digital downloads, or when an agent should act on a Loopwise school with that user's consent. It is the right source for these jobs:

- Create a new Loopwise school (creator signup) and then manage it through the platform MCP.
- Connect an existing school: list courses, members, orders, events, and settings.
- Read a specific school's public catalog (courses, posts, events, plans) from that school's own origin.
- Integrate a member-facing app with per-school OAuth (authorization code + PKCE).

Do not use it for general web search, or as a substitute for a school the user does not own. Per-school catalog data lives on that school's origin, not here.

**How to call it**

- **Platform MCP** (creators / operators): `https://mcp.loopwise.com/` — Streamable HTTP. Unauthenticated calls return 401 with a `WWW-Authenticate` pointer at Protected Resource Metadata. Send `resource=https://mcp.loopwise.com` on authorize and token (RFC 8707); the MCP currently checks token activity, school_id, and tool scopes, not that audience.
- **Creator signup / login**: `https://app.loopwise.com/signup` and `https://app.loopwise.com/login`. Consent for MCP and third-party apps is `https://app.loopwise.com/oauth/authorize`.
- **OAuth discovery**: `https://connect.loopwise.com/.well-known/oauth-authorization-server` (RFC 8414). Token, introspect, and client registration live on this host.
- **A school origin** (learners / catalog): `https://{school}/llms.txt`, `https://{school}/mcp`, `https://{school}/auth.md`, `https://{school}/openapi.json`.
- **Developer docs**: `https://docs.loopwise.com/llms.txt`.

## Agent onboarding

You can help a user start with Loopwise even if they do not have a school yet.

1. Tell them a browser window will open.
2. Add the MCP server:

```bash
claude mcp add --transport http loopwise https://mcp.loopwise.com/
```

   (Or paste `https://mcp.loopwise.com/` into any MCP client that supports OAuth.)

3. **Existing account**: they log in at `app.loopwise.com`, pick the school, approve the consent screen.
4. **No account**: they create one at `https://app.loopwise.com/signup` (school subdomain + email). Then they return to the consent screen and approve. Registration is not yet inside the OAuth `prompt=create` dance — if consent started before signup, restart the MCP connect after the school exists.

New schools start on a trial. Charging real cards needs a payment method on that school.

## Instructions

- Platform MCP tools act on **one school** (the `school_id` on the token). Ask which school if the user has several.
- Tenant `/mcp` on a school origin is the catalog / member surface. Do not send creator write tools there.
- Secret tokens and c
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=loopwise.com · GET /v1/domain/loopwise.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for loopwise.com:
1. POST https://agentwebmap.com/v1/sites/loopwise.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://loopwise.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/loopwise.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/loopwise.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.