involve.me website screenshot

involve.me

involve.me is an AI quiz, form and funnel builder with built-in email automation and a lightweight CRM, operated by stereosense GmbH and used by marketing teams to capture, qualify and follow up on leads. Customers build quizzes, assessments, calculators, product finders, landing pages, surveys and payment pages in a no-code editor, publish them as a hosted page or an embedded widget, and route submissions into 55+ native CRM and email destinations. Its programmable surface is deliberately narrow: there is no public REST API and no OpenAPI, and the only machine-addressable paths are an outbound webhook that fires when a participant completes a funnel (Scale plan and above), a copy-paste JavaScript embed loader, Zapier and Make connectors, and an OAuth-protected Model Context Protocol server that exposes the marketing website's Statamic CMS rather than the product itself.

involve.me publishes 1 API on the APIs.io network. Tagged areas include Company, Marketing, Lead Generation, Forms, and Surveys.

The involve.me catalog on APIs.io includes 1 event-driven AsyncAPI specification.

involve.me’s developer surface includes documentation, support, engineering blog, pricing, signup flow, authentication, and 24 more developer resources.

49.1/100 developing ▬ flat Agent 31/100 agent ready saas Full breakdown ↓
scored 2026-09-06 · rubric v0.19.0
AccessFreemiumSelf serve⚡ Free to try
1 APIs 1 MCP Servers
CompanyMarketingLead GenerationFormsSurveysQuizzesNo-CodeEmail MarketingCRMWebhookMCPAustria

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-06 · rubric v0.19.0
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/involve-me: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

involve.me Website Content MCP Server

A live, OAuth-protected Model Context Protocol server that involve.me serves from its own infrastructure and advertises through RFC 9728 protected-resource metadata on www.invol...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

involve.me Statamic Content MCP

involve.me serves a live, OAuth-protected Model Context Protocol server. It is advertised by RFC 9728 protected-resource metadata on the public marketing host and it answers. IM...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Involve Me Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Involve Me Authentication

5 schemes

SECURITY

Involve Me Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Involve Me Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Involve Me Trust Center

SOC 2 Type II, GDPR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Involve Me Scopes

21 scopes

21 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 2

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: involve-me
name: involve.me
description: 'involve.me is an AI quiz, form and funnel builder with built-in email automation and a lightweight CRM, operated
  by stereosense GmbH and used by marketing teams to capture, qualify and follow up on leads. Customers build quizzes, assessments,
  calculators, product finders, landing pages, surveys and payment pages in a no-code editor, publish them as a hosted page
  or an embedded widget, and route submissions into 55+ native CRM and email destinations. Its programmable surface is deliberately
  narrow: there is no public REST API and no OpenAPI, and the only machine-addressable paths are an outbound webhook that
  fires when a participant completes a funnel (Scale plan and above), a copy-paste JavaScript embed loader, Zapier and Make
  connectors, and an OAuth-protected Model Context Protocol server that exposes the marketing website''s Statamic CMS rather
  than the product itself.'
url: https://raw.githubusercontent.com/api-evangelist/involve-me/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.involve.me/favicons/favicon-32x32.png
x-type: company
x-source: harvest:marketing-integration-graph
x-tier: profiled
x-tier-reason: Upgraded from stub by the local enrichment pass on 2026-08-12. Real provider artifacts were harvested verbatim
  (llms.txt, RFC 9116 security.txt, RFC 8414 and RFC 9728 OAuth metadata) and a live gated MCP server was probed, but no OpenAPI
  or public REST API exists.
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Marketing
- Lead Generation
- Forms
- Surveys
- Quizzes
- No-Code
- Email Marketing
- CRM
- Webhook
- MCP
- Austria
tags_raw:
- Company
- Marketing
- Lead Generation
- Forms
- Surveys
- Quizzes
- No-Code
- Email Marketing
- CRM
- Webhooks
- Model Context Protocol
- Austria
apis:
- name: involve.me Website Content MCP Server
  description: 'A live, OAuth-protected Model Context Protocol server that involve.me serves from its own infrastructure and
    advertises through RFC 9728 protected-resource metadata on www.involve.me. SCOPE: it exposes the Statamic CMS behind the
    involve.me MARKETING WEBSITE — entries, collections, taxonomy terms, assets, globals and blueprints — not the involve.me
    funnel product. There is no MCP, REST or GraphQL interface to funnels, submissions, participants, contacts or email sequences.
    The tool list is auth-gated (JSON-RPC tools/list returns 401 with a spec-correct WWW-Authenticate Bearer challenge), so
    no tool schemas have been recorded.'
  humanURL: https://www.involve.me/
  baseURL: https://www-cdn.involve.me/mcp/statamic
  tags:
  - MCP
  - Content Management
  - Authentication
  tags_raw:
  - Model Context Protocol
  - Content Management
  - OAuth
  properties:
  - type: MCPServer
    url: mcp/involve-me-mcp.yml
  - type: Authentication
    url: authentication/involve-me-authentication.yml
  - type: OAuthScopes
    url: scopes/involve-me-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/involve-me-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/involve-me-vulnerability-disclosure.yml
- type: Security
  url: security/involve-me-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/involve-me-domain-security.yml
- type: Website
  url: https://www.involve.me/
- type: Documentation
  url: https://help.involve.me/en/
- type: Support
  url: https://www.involve.me/contact
- type: Blog
  url: https://www.involve.me/blog
- type: Pricing
  url: https://www.involve.me/pricing
- type: SignUp
  url: https://app.involve.me/register
- type: Login
  url: https://app.involve.me/login
- type: TermsOfService
  url: https://www.involve.me/terms
- type: PrivacyPolicy
  url: https://www.involve.me/privacy
- type: GitHubOrganization
  url: https://github.com/stereosense
- type: StatusPage
  url: https://status.involve.me/
- type: Integrations
  url: https://www.involve.me/integrations
- type: DataProcessingAgreement
  url: https://www.involve.me/data-processing
- type: LLMsTxt
  url: llms/involve-me-llms.txt
- type: WellKnown
  url: well-known/involve-me-well-known.yml
- type: SecurityTxt
  url: well-known/involve-me-security.txt
- type: Webhooks
  url: asyncapi/involve-me-webhooks.yml
- type: Authentication
  url: authentication/involve-me-authentication.yml
- type: OAuthScopes
  url: scopes/involve-me-scopes.yml
- type: MCPServer
  url: mcp/involve-me-mcp.yml
- type: Conformance
  url: conformance/involve-me-conformance.yml
- type: Compliance
  url: conformance/involve-me-conformance.yml
- type: Lifecycle
  url: lifecycle/involve-me-lifecycle.yml
- type: Plans
  url: plans/involve-me-plans-pricing.yml
- type: Conventions
  url: conventions/involve-me-conventions.yml
- type: Components
  url: components/involve-me-components.yml
- type: DataModel
  url: data-model/involve-me-data-model.yml
x-pointers-deliberately-omitted:
  note: These artifacts exist in the repo and record an honest ABSENCE. No common[] pointer is emitted for them, because the
    pointer asserts the provider publishes that surface — the same rule this pipeline applies to a well-known probe where
    every path 404s. Emitting them would credit involve.me for documents it does not serve.
  omitted:
  - type: ChangeLog
    artifact: changelog/involve-me-changelog.yml
    reason: No changelog exists. /changelog, /release-notes, /product-updates, /whats-new and /updates all return 404; the
      nearest equivalent is a marketing blog category.
  - type: RateLimits
    artifact: rate-limits/involve-me-rate-limits.yml
    reason: limit_count is 0 — no rate limits are published, because no API is published.
  - type: Packages
    artifact: packages/involve-me-packages.yml
    reason: package_count is 0 — no first-party client library exists on npm, PyPI, Packagist or any other registry, and neither
      GitHub org publishes one.
  - type: SDKs
    artifact: packages/involve-me-packages.yml
    reason: official_sdk_count is 0.
  - type: Deprecation
    artifact: lifecycle/involve-me-lifecycle.yml
    reason: No deprecation or sunset policy is published; the Lifecycle artifact records that absence alongside the StatusPage
      hit.
  - type: Idempotency
    artifact: conventions/involve-me-conventions.yml
    reason: No idempotency mechanism exists on either surface, and involve.me publishes no delivery-identifier guarantee a
      receiver could deduplicate on.
  - type: AgentCard
    artifact: null
    reason: /.well-known/agent-card.json and /.well-known/agent.json return 404 on www., app. and api.involve.me. Nothing
      was written to a2a/ — an agent card is never authored on a provider's behalf.
x-vouched-by:
- Drip
- MailerLite
x-vouch-count: 2
x-not-duplicate-of: involveai -- involve.ai is an AI customer-intelligence platform for customer success teams; involve.me
  is a marketing funnel builder. Different companies, verified 2026-08-12.
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 21
  pass: local-v1
x-coverage:
  state: covered
  reason: partial-surface
  detail: 'Four provider-published documents were harvested verbatim (llms.txt, an RFC 9116 security.txt, and RFC 8414 + RFC
    9728 OAuth metadata) and a live OAuth-gated MCP server was probed, but involve.me publishes no OpenAPI and no public REST
    API: developers.involve.me and docs.involve.me both 302 into involve.me''s own funnel-hosting edge with utm_campaign=customer_organization-deleted,
    and api.involve.me answers 404 at every probed path.'
  evidence:
  - url: https://www.involve.me/.well-known/oauth-protected-resource
    status: 200
  - url: https://www.involve.me/llms.txt
    status: 200
  - url: https://app.involve.me/.well-known/security.txt
    status: 200
  - url: https://www-cdn.involve.me/mcp/statamic
    status: 401
  - url: https://developers.involve.me/
    status: 302
  - url: https://docs.involve.me/
    status: 302
  - url: https://api.involve.me/openapi.json
    status: 404
  checked: '2026-08-12'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/involve-me"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/involve-me/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/involve-me/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.