MicroTransponder

MicroTransponder, Inc. — renamed Mobia Medical, Inc. on 2026-02-24 — is a privately founded, Austin/Dallas Texas medical device company that develops the FDA-approved Vivistim Paired VNS System, an implantable vagus nerve stimulation device paired with rehabilitation therapy to reduce upper-extremity motor deficits in chronic ischemic stroke survivors. The company is a medical device manufacturer, not a software vendor: it publishes no developer portal, no product API, no SDKs and no public source repositories. The only machine-readable surface API Evangelist could reach on hosts the company controls is the WordPress REST API behind its corporate site (www.mobia.com) and its product site (www.vivistim.com), plus an OAuth-protected Model Context Protocol endpoint the corporate site serves via the WordPress MCP Adapter, with RFC 8414 and RFC 9728 discovery documents. This profile records that surface and nothing more.

MicroTransponder publishes 1 API on the APIs.io network. Tagged areas include Company, Medical Devices, Healthcare, Neurotechnology, and Neuromodulation.

MicroTransponder’s developer surface includes support, engineering blog, authentication, and 19 more developer resources.

🌐 Visit website 📡 Source on GitHub

21.6/100 emerging ▬ flat Agent 23/100 agent aware saas Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0

AccessSelf serve

1 APIs 1 MCP Servers

Company Medical Devices Healthcare Neurotechnology NeuromodulationStroke RehabilitationImplantable Devices Life Sciences WordPress MCP

Kin Score

Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0

Composite quality — 21.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 3.0 / 17

Access Clarity 3.1 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.8 / 9

Regulatory Posture 8.1 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Surface 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

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/microtransponder: 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.

Mobia Medical Site REST API (WordPress)

The WordPress REST API served by the Mobia Medical corporate site at https://www.mobia.com/wp-json/. It is the content-management API behind the marketing site — 320 routes acro...

MCP Servers 1

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

Rate Limits 1

Documented rate limits and quota policies.

Scopes 1

OAuth scopes governing access to this provider's APIs.

Microtransponder Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

MCPServer

MCPServer

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Lifecycle

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

Compliance

Authentication

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 4

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

LinkedIn

Other 1

Properties that don't map to a standard resource type

ProductSite

ProductSite

Source (apis.yml)

aid: microtransponder
name: MicroTransponder
description: 'MicroTransponder, Inc. — renamed Mobia Medical, Inc. on 2026-02-24 — is a privately founded, Austin/Dallas Texas
  medical device company that develops the FDA-approved Vivistim Paired VNS System, an implantable vagus nerve stimulation
  device paired with rehabilitation therapy to reduce upper-extremity motor deficits in chronic ischemic stroke survivors.
  The company is a medical device manufacturer, not a software vendor: it publishes no developer portal, no product API, no
  SDKs and no public source repositories. The only machine-readable surface API Evangelist could reach on hosts the company
  controls is the WordPress REST API behind its corporate site (www.mobia.com) and its product site (www.vivistim.com), plus
  an OAuth-protected Model Context Protocol endpoint the corporate site serves via the WordPress MCP Adapter, with RFC 8414
  and RFC 9728 discovery documents. This profile records that surface and nothing more.'
url: https://raw.githubusercontent.com/api-evangelist/microtransponder/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: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
image: https://www.mobia.com/wp-content/uploads/2026/04/mobia-social-image.jpg
x-type: company
x-source: harvest:secondary-market
x-former-name: MicroTransponder, Inc.
x-current-name: Mobia Medical, Inc.
specificationVersion: '0.20'
created: '2026-08-25'
modified: '2026-08-26'
tags:
- Company
- Medical Devices
- Healthcare
- Neurotechnology
- Neuromodulation
- Stroke Rehabilitation
- Implantable Devices
- Life Sciences
- WordPress
- MCP
tags_raw:
- Company
- Medical Devices
- Health Care
- Neurotechnology
- Neuromodulation
- Stroke Rehabilitation
- Implantable Devices
- Life Sciences
- WordPress
- Model Context Protocol
apis:
- name: Mobia Medical Site REST API (WordPress)
  description: The WordPress REST API served by the Mobia Medical corporate site at https://www.mobia.com/wp-json/. It is
    the content-management API behind the marketing site — 320 routes across 22 namespaces including wp/v2 (posts, pages,
    media, news, team), wp-abilities/v1 and an mcp namespace — not a Vivistim product or device API. Anonymous reads are open;
    writes and the MCP endpoints require authentication.
  humanURL: https://www.mobia.com/wp-json/
  baseURL: https://www.mobia.com/wp-json/
  tags:
  - Content Management
  - WordPress
  - REST
  properties:
  - type: APIDiscovery
    url: discovery/microtransponder-wp-rest-routes.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/microtransponder-domain-security.yml
- type: Website
  url: https://www.mobia.com/
- type: ProductSite
  url: https://www.vivistim.com/
- type: Support
  url: https://www.mobia.com/contact-us/
- type: Blog
  url: https://ir.mobia.com/news-events/press-releases/
- type: BlogRSS
  url: https://www.mobia.com/feed/
- type: PrivacyPolicy
  url: https://www.mobia.com/privacy-policy/
- type: Compliance
  url: https://www.mobia.com/compliance/
- type: LinkedIn
  url: https://www.linkedin.com/company/microtransponder
- type: WellKnown
  url: well-known/microtransponder-well-known.yml
- type: MCPServer
  url: mcp/microtransponder-mcp.yml
- type: Authentication
  url: authentication/microtransponder-authentication.yml
- type: OAuthScopes
  url: scopes/microtransponder-scopes.yml
- type: ErrorCatalog
  url: errors/microtransponder-problem-types.yml
- type: Conventions
  url: conventions/microtransponder-conventions.yml
- type: DataModel
  url: data-model/microtransponder-data-model.yml
- type: Lifecycle
  url: lifecycle/microtransponder-lifecycle.yml
- type: Conformance
  url: conformance/microtransponder-conformance.yml
- type: RateLimits
  url: rate-limits/microtransponder-rate-limits.yml
- type: Plans
  url: plans/microtransponder-plans-pricing.yml
- type: Packages
  url: packages/microtransponder-packages.yml
- type: LLMsTxt
  url: llms/microtransponder-llms.txt
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 17
  pass: local-v1
x-coverage:
  state: covered
  reason: no-developer-program
  detail: MicroTransponder (renamed Mobia Medical on 2026-02-24) is an implantable medical device maker with no developer
    program — every contract-discovery path missed on every host — but its corporate WordPress site does serve two real /.well-known
    OAuth documents and two live, OAuth-gated Model Context Protocol endpoints, which is what this profile records.
  evidence:
  - url: https://www.mobia.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://www.mobia.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://www.mobia.com/openapi.json
    status: 404
  - url: https://api.github.com/orgs/microtransponder
    status: 404
  checked: '2026-08-26'

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/microtransponder"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/microtransponder/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/microtransponder/evidence"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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