aiCTX (now SynSense) · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the SynSense Website Content API

5 actions 5 updates update extends ../openapi/aictx-website-content-api-openapi.json
Derived by API Evangelist Built from the contracts aiCTX (now SynSense) publishes. aiCTX (now SynSense) did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-providerx-provider-former-namex-provider-renamedx-provider-websitex-provider-industryx-apievangelist-profilex-product-surfacex-tls

Targets 4

$.info
$.servers[0]
$.paths[*].get
$.components.schemas

OpenAPI Overlay

aictx-website-content-api-overlay.yaml Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the SynSense Website Content API
  version: 1.0.0
extends: ../openapi/aictx-website-content-api-openapi.json
x-generated: '2026-09-14'
x-method: generated
x-source: >-
  API Evangelist enrichment pipeline. Captures the enhancements this profile adds on top of the
  document derived from https://www.synsense.ai/wp-json — provider identity, the rename, the
  runtime facts observed on the wire, and cross-links to the sibling artifacts in this repo. The
  base document is never mutated.
actions:
- target: $.info
  description: Attach provider identity and the aiCTX -> SynSense rename to the contract itself.
  update:
    x-provider: SynSense AG
    x-provider-former-name: aiCTX AG
    x-provider-renamed: '2020-05'
    x-provider-website: https://www.synsense.ai/
    x-provider-industry: Neuromorphic computing and edge AI silicon
    x-apievangelist-profile: https://apis.io/provider/aictx
- target: $.info
  description: >-
    State plainly that the product surface is not this API, so an agent reading only the contract
    does not conclude SynSense's hardware is network-callable.
  update:
    x-product-surface: >-
      SynSense's neuromorphic processors are programmed through local Python libraries (Samna,
      Rockpool, Sinabs) over USB/FPGA development kits. There is no network API for the silicon.
      This contract covers the corporate website's content only.
- target: $.servers[0]
  description: Record the observed transport posture of the single server.
  update:
    x-tls: TLSv1.3
    x-hsts-max-age: 31536000
    x-cors-allow-origin: '*'
    x-observed: '2026-09-14'
- target: $.paths[*].get
  description: >-
    Mark every described operation as safe and anonymous. The public surface answers `Allow: GET`
    and refuses anonymous writes with 401.
  update:
    x-safe: true
    x-auth-required: false
    x-agentic-access:
      action_class: read
      consequence: none
      token: none
      escalation: none
- target: $.components.schemas
  description: Cross-link the derived artifacts that explain this contract at runtime.
  update:
    x-apievangelist-artifacts:
      conventions: conventions/aictx-conventions.yml
      errors: errors/aictx-problem-types.yml
      authentication: authentication/aictx-authentication.yml
      data_model: data-model/aictx-data-model.yml
      conformance: conformance/aictx-conformance.yml
      rate_limits: rate-limits/aictx-rate-limits.yml
      skills: skills/_index.yml

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • 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 overlay
curl "https://apis.io/api/v1/overlays/aictx-website-content-api-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

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