Inrupt

aid: inrupt
name: Inrupt
description: Inrupt is the enterprise company founded by Sir Tim Berners-Lee and John Bruce to commercialize Solid, the open
  decentralized-data specification he created at MIT. Its flagship product is the Enterprise Solid Server (ESS), a Kubernetes-deployed
  platform of cooperating services that gives each person or organization a Pod — a personal data store with fine-grained
  access control, auditing, and W3C Verifiable-Credential-based Access Requests and Grants. ESS ships an Access Grant service,
  an Authorization service using Access Control Policies (ACP), a Pod Storage service implementing the Solid Protocol, a Notification
  Delivery service that pushes signed webhooks to remote HTTPS endpoints, a Platform Management service with a token-exchange
  and admin provisioning API, an optional hybrid keyword-plus-semantic Search service, and — since ESS 3.0 — an MCP Resource
  Service exposing consent-mediated tools to AI agents. Inrupt also runs PodSpaces, a hosted developer-preview deployment
  of ESS, and publishes first-party JavaScript and Java client SDKs.
url: https://raw.githubusercontent.com/api-evangelist/inrupt/refs/heads/main/apis.yml
image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-23'
modified: '2026-08-23'
tags:
- Company
- Solid
- Personal Data Stores
- Decentralized Identity
- Data Privacy
- Access Control
- Verifiable Credentials
- Linked Data
- RDF
- Consent Management
- Data Wallets
- Agent Infrastructure
- Model Context Protocol
- Enterprise Software
apis:
- aid: inrupt:notification-delivery
  name: Inrupt Change Notifications API (ESS Notification Delivery Service)
  description: The ESS Notification Delivery Service lets an authorized agent subscribe to change events on Pod resources
    and on Access Requests/Grants, and have them delivered as signed webhooks to a remote HTTPS endpoint. Subscriptions are
    created and managed over a REST API described by a first-party OpenAPI 3.1.0 document the service serves itself at /openapi.
    Fourteen operations cover protocol negotiation, the JWKS used to verify outbound message signatures, user subscriptions,
    system subscriptions, delivery-failure listings, and reprocessing of failed deliveries.
  humanURL: https://docs.inrupt.com/ess/services/service-notification/notification-delivery-service
  baseURL: https://notification.inrupt.com
  tags:
  - Notifications
  - Webhooks
  - Events
  - Subscriptions
  properties:
  - type: OpenAPI
    url: openapi/inrupt-notification-openapi.yaml
  - type: Documentation
    url: https://docs.inrupt.com/ess/services/service-notification/notification-delivery-service
  - type: Webhooks
    url: asyncapi/inrupt-notifications-webhooks.yml
- aid: inrupt:pod-storage
  name: Inrupt Pod Storage API (Solid Protocol)
  description: The ESS Pod Storage Service implements the Solid Protocol over HTTP — LDP-style container and resource CRUD
    in RDF (Turtle, JSON-LD) and binary form, with Access Control Policy (ACP) resources, canonical /sc/ and path-based /sp/
    resource URIs, and a Data Views API that projects stored resources through registered GraphQL view definitions. On the
    hosted PodSpaces deployment the storage host is https://storage.inrupt.com and its discovery document is served at /.well-known/solid.
  humanURL: https://docs.inrupt.com/ess/services/service-pod-management/service-pod-storage
  baseURL: https://storage.inrupt.com
  tags:
  - Storage
  - Solid Protocol
  - RDF
  - Access Control
  properties:
  - type: Documentation
    url: https://docs.inrupt.com/ess/services/service-pod-management/service-pod-storage
  - type: WellKnown
    url: well-known/inrupt-well-known.yml
- aid: inrupt:solid-oidc
  name: Inrupt Solid OpenID Provider
  description: Inrupt's hosted Solid-OIDC identity provider for PodSpaces WebIDs. It publishes a standard OpenID Connect discovery
    document at /.well-known/openid-configuration advertising authorization, token, userinfo, JWKS, dynamic client registration,
    revocation and end-session endpoints, the openid / offline_access / webid scopes, and DPoP proof signing algorithms.
  humanURL: https://docs.inrupt.com/guides/authentication-in-solid
  baseURL: https://login.inrupt.com
  tags:
  - Authentication
  - OpenID Connect
  - Solid-OIDC
  - DPoP
  properties:
  - type: OpenIDConnect
    url: well-known/inrupt-openid-configuration.json
  - type: Documentation
    url: https://docs.inrupt.com/guides/authentication-in-solid
  - type: Authentication
    url: authentication/inrupt-authentication.yml
  - type: OAuthScopes
    url: scopes/inrupt-scopes.yml
- aid: inrupt:access-grant
  name: Inrupt Access Grant Service (VC API)
  description: The ESS Access Grant Service issues, queries, verifies, derives and status-checks W3C Verifiable Credentials
    that carry Access Requests and Access Grants — the consent receipts that authorize one agent to read another agent's Pod
    resources. The service publishes its endpoint map at /.well-known/vc-configuration; on PodSpaces that is https://vc.inrupt.com,
    which advertises the /issue, /status, /verify, /derive and /query services and Ed25519Signature2020 proofs.
  humanURL: https://docs.inrupt.com/ess/services/service-access-grant
  baseURL: https://vc.inrupt.com
  tags:
  - Verifiable Credentials
  - Consent
  - Authorization
  - Access Grants
  properties:
  - type: Documentation
    url: https://docs.inrupt.com/ess/services/service-access-grant
  - type: WellKnown
    url: well-known/inrupt-vc-configuration.json
- aid: inrupt:mcp-resource
  name: Inrupt ESS MCP Resource Service
  description: Added in ESS 3.0, the MCP Resource Service exposes four Model Context Protocol tools — requestAccess, checkAccessRequestStatus,
    hasMatchingAccessGrant and getResource — over streamable HTTP, so an AI agent can ask a person for consent to their Pod
    data, wait for the approval, and then read the granted resource. Every operation is scoped to the authenticated delegator,
    so an agent can never exceed the current user's own access rights. The endpoint is per-deployment (https://mcp.{ess-domain}/api)
    and is authenticated with an ESS Access Token obtained by OAuth 2.0 token exchange against the Platform Management service.
  humanURL: https://docs.inrupt.com/ess/services/service-mcp/mcp-resource
  baseURL: https://mcp.{ess-domain}/api
  tags:
  - Model Context Protocol
  - AI Agents
  - Consent
  - Access Grants
  properties:
  - type: MCPServer
    url: mcp/inrupt-mcp.yml
  - type: ToolCrosswalk
    url: mcp/inrupt-tool-crosswalk.yml
  - type: Documentation
    url: https://docs.inrupt.com/ess/services/service-mcp/mcp-resource
- aid: inrupt:platform-management
  name: Inrupt ESS Platform Management API
  description: The Platform Management service hosts the ESS Admin API used to provision users before they first log in —
    creating a provisioning account, attaching a WebID and a storage container, setting identity mappings, then activating
    the account and transferring ownership to the end user — plus self-service /user/account endpoints and the OAuth 2.0 token-exchange
    endpoint (RFC 8693) that turns an external IdP id_token into an ESS Access Token. Access to the Admin API is restricted
    to Service Accounts.
  humanURL: https://docs.inrupt.com/ess/services/service-platform-management/platform-management-api
  baseURL: https://platform.inrupt.com
  tags:
  - Provisioning
  - Administration
  - Token Exchange
  - Identity
  properties:
  - type: Documentation
    url: https://docs.inrupt.com/ess/services/service-platform-management/platform-management-api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.inrupt.com/
- type: DeveloperPortal
  url: https://docs.inrupt.com/
- type: Documentation
  url: https://docs.inrupt.com/
- type: APIReference
  url: https://docs.inrupt.com/ess/services/
- type: GettingStarted
  url: https://docs.inrupt.com/sdk/javascript-sdk/tutorial/
- type: Support
  url: https://inrupt.atlassian.net/servicedesk
- type: Blog
  url: https://www.inrupt.com/blog
- type: GitHubOrganization
  url: https://github.com/inrupt
- type: SignUp
  url: https://start.inrupt.com/
- type: TermsOfService
  url: https://www.inrupt.com/terms-conditions
- type: PrivacyPolicy
  url: https://www.inrupt.com/privacy-policy
- type: StatusPage
  url: https://status.inrupt.com/
- type: Deprecation
  url: https://www.inrupt.com/maintenance-policy
- type: Security
  url: https://www.inrupt.com/security
- type: TrustCenter
  url: https://www.inrupt.com/trust
- type: Compliance
  url: conformance/inrupt-conformance.yml
- type: LLMsTxt
  url: llms/inrupt-llms.txt
- type: Packages
  url: packages/inrupt-packages.yml
- type: SDKs
  url: packages/inrupt-packages.yml
- type: WellKnown
  url: well-known/inrupt-well-known.yml
- type: MCPServer
  url: mcp/inrupt-mcp.yml
- type: ToolCrosswalk
  url: mcp/inrupt-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Conformance
  url: conformance/inrupt-conformance.yml
- type: ErrorCatalog
  url: errors/inrupt-problem-types.yml
- type: Lifecycle
  url: lifecycle/inrupt-lifecycle.yml
- type: ChangeLog
  url: changelog/inrupt-changelog.yml
- type: OAuthScopes
  url: scopes/inrupt-scopes.yml
- type: Authentication
  url: authentication/inrupt-authentication.yml
- type: DomainSecurity
  url: security/inrupt-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/inrupt-vulnerability-disclosure.yml
- type: Sandbox
  url: sandbox/inrupt-sandbox.yml
- type: Conventions
  url: conventions/inrupt-conventions.yml
- type: DataModel
  url: data-model/inrupt-data-model.yml
- type: Webhooks
  url: asyncapi/inrupt-notifications-webhooks.yml
- type: Plans
  url: plans/inrupt-plans-pricing.yml
- type: RateLimits
  url: rate-limits/inrupt-rate-limits.yml
- type: Overlay
  url: overlays/inrupt-notification-overlay.yaml
x-enrichment:
  date: '2026-08-23'
  status: enriched
  artifacts_added: 28
  pass: local-v1
x-coverage:
  state: covered
  reason: contract-discovered
  detail: STEP 0b paid off. The docs host and the marketing host return 404 for every /openapi path, but the ESS Notification
    Delivery Service serves its own OpenAPI 3.1.0 ("Inrupt Change Notifications", v2.7.1, 14 operations) at https://notification.inrupt.com/openapi.yaml
    - a location named only in one paragraph of the service reference. The remaining ESS services (Access Grant, Pod Storage,
    Platform Management, Search) publish endpoint tables in prose and RDF/JSON discovery documents but no OpenAPI.
  evidence:
  - url: https://notification.inrupt.com/openapi.yaml
    status: 200
  - url: https://docs.inrupt.com/llms.txt
    status: 200
  - url: https://login.inrupt.com/.well-known/openid-configuration
    status: 200
  - url: https://storage.inrupt.com/.well-known/solid
    status: 200
  - url: https://vc.inrupt.com/.well-known/vc-configuration
    status: 200
  - url: https://docs.inrupt.com/openapi.json
    status: 404
  checked: '2026-08-23'