GigaIO

GigaIO is a Carlsbad, California hardware and software company building datacenter-class computing for the edge. Its current product line is Gryf, a carry-on suitcase-sized, ruggedized, field-serviceable AI supercomputer built from hot-swappable Accelerator, Compute, Network and Storage sleds, plus Manticore for larger deployments. The company was founded around FabreX, a PCIe/CXL-based composable memory fabric that disaggregates GPUs, FPGAs, NVMe and DRAM into dynamically composed clusters and is managed with DMTF Redfish RESTful APIs and a FabreX CLI that integrates with Ansible, Chef, Puppet, Slurm, OpenPBS, LSF and Kubernetes. In April 2026 GigaIO sold its datacenter technology and assets — including SuperNODE and FabreX — to d-Matrix, and refocused the company on edge AI inferencing. GigaIO publishes no public developer portal, API reference or machine-readable specification; the API documentation and knowledge base sit behind its Atlassian-hosted customer support portal. It does run a remote Model Context Protocol server on gigaio.com, protected by OAuth 2.0 with PKCE.

GigaIO is profiled on the APIs.io network. Tagged areas include Company, Composable Infrastructure, Edge Computing, Artificial Intelligence, and High Performance Computing.

GigaIO’s developer surface includes support, engineering blog, authentication, CLI, and 14 more developer resources.

19.1/100 emerging ▬ flat Agent 20/100 agent aware Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
0 APIs 1 MCP Servers
CompanyComposable InfrastructureEdge ComputingArtificial IntelligenceHigh Performance ComputingData CenterHardwareGPUPCIeInfrastructure as Code

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 19.1/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 5.2 / 20
Access Clarity 5.5 / 20
Operational Transparency 0.0 / 13
Contract Governance 2.2 / 12
Discoverability 6.1 / 10
Agent readiness — 20/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 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/gigaio: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

MCP Servers 1

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

GigaIO MCP Server

GigaIO runs a remote Model Context Protocol server on its own domain at https://gigaio.com/wp-json/mcp/mcp-oauth-server, advertised through an RFC 9728 protected-resource docume...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Gigaio Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Gigaio Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Gigaio Authentication

1 scheme

SECURITY

Gigaio Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Gigaio Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: gigaio
name: GigaIO
description: GigaIO is a Carlsbad, California hardware and software company building datacenter-class computing for the edge.
  Its current product line is Gryf, a carry-on suitcase-sized, ruggedized, field-serviceable AI supercomputer built from hot-swappable
  Accelerator, Compute, Network and Storage sleds, plus Manticore for larger deployments. The company was founded around FabreX,
  a PCIe/CXL-based composable memory fabric that disaggregates GPUs, FPGAs, NVMe and DRAM into dynamically composed clusters
  and is managed with DMTF Redfish RESTful APIs and a FabreX CLI that integrates with Ansible, Chef, Puppet, Slurm, OpenPBS,
  LSF and Kubernetes. In April 2026 GigaIO sold its datacenter technology and assets — including SuperNODE and FabreX — to
  d-Matrix, and refocused the company on edge AI inferencing. GigaIO publishes no public developer portal, API reference or
  machine-readable specification; the API documentation and knowledge base sit behind its Atlassian-hosted customer support
  portal. It does run a remote Model Context Protocol server on gigaio.com, protected by OAuth 2.0 with PKCE.
image: https://gigaio.com/wp-content/uploads/2020/09/logo.svg
url: https://raw.githubusercontent.com/api-evangelist/gigaio/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-21'
modified: '2026-08-21'
tags:
- Company
- Composable Infrastructure
- Edge Computing
- Artificial Intelligence
- High Performance Computing
- Data Center
- Hardware
- GPU
- PCIe
- Infrastructure as Code
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/gigaio-domain-security.yml
- type: Website
  url: https://gigaio.com/
- type: Support
  url: https://gigaio.com/support/
- type: Login
  url: https://gigaio.com/sign-in-to-gigaio-support/
- type: Blog
  url: https://gigaio.com/news/
- type: TermsOfService
  url: https://gigaio.com/terms-of-use/
- type: PrivacyPolicy
  url: https://gigaio.com/privacy-policy/
- type: WellKnown
  url: well-known/gigaio-well-known.yml
- type: MCPServer
  url: mcp/gigaio-mcp.yml
- type: Authentication
  url: authentication/gigaio-authentication.yml
- type: OAuthScopes
  url: scopes/gigaio-scopes.yml
- type: Conformance
  url: conformance/gigaio-conformance.yml
- type: Conventions
  url: conventions/gigaio-conventions.yml
- type: Lifecycle
  url: lifecycle/gigaio-lifecycle.yml
- type: Plans
  url: plans/gigaio-plans-pricing.yml
- type: RateLimits
  url: rate-limits/gigaio-rate-limits.yml
- type: CLI
  url: cli/gigaio-cli.yml
- type: LLMsTxt
  url: llms/gigaio-llms.txt
x-enrichment:
  date: '2026-08-21'
  status: enriched
  artifacts_added: 15
  pass: local-v1
x-coverage:
  state: covered
  reason: null
  detail: GigaIO ships no public developer program — its FabreX/Redfish API reference and knowledge base sit behind an Atlassian
    Jira Service Management customer login at gigaio.atlassian.net, and the FabreX CLI page tells readers to "CONTACT US for
    details on APIs" — but STEP 0b contract discovery did not come back empty. GigaIO deliberately runs a remote, OAuth-protected
    Model Context Protocol server on its own host at https://gigaio.com/wp-json/mcp/mcp-oauth-server, advertised by RFC 8414
    and RFC 9728 discovery documents that were captured verbatim here. The `mcp` REST namespace is not a WordPress or WP Engine
    default (wpengine.com, ma.tt and techcrunch.com expose wp-abilities/v1 but no mcp namespace), so it was installed on purpose.
    The tool list itself is auth-gated and was not introspected.
  evidence:
  - url: https://gigaio.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://gigaio.com/.well-known/oauth-authorization-server
    status: 200
  - url: https://gigaio.com/wp-json/mcp/mcp-oauth-server
    status: 401
  - url: https://gigaio.com/sign-in-to-gigaio-support/
    status: 200
  - url: https://gigaio.com/openapi.json
    status: 404
  - url: https://gigaio.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-21'

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/gigaio"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/gigaio/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/gigaio/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.