Service Mesh Interface (SMI)

SMI Traffic Specs

Traffic Specs describes a set of resources that allow users to specify how their traffic looks. It is used in concert with access control and other policies to concretely define what should happen to specific types of traffic as it flows through the mesh. Defines `HTTPRouteGroup`, `TCPRoute`, and `UDPRoute` resources.

GitHub

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./json-schema/http-route-group-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./json-schema/tcp-route-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./json-schema/udp-route-schema.json

Other Resources

🔗
APIVersion
🔗
Kind
🔗
Kind
🔗
Kind
🔗
Specification
https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-specs/v1alpha4/traffic-specs.md
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./examples/http-route-group-example.yaml
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./examples/tcp-route-example.yaml
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/service-mesh-interface/refs/heads/main/./examples/udp-route-example.yaml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/smi-traffic-specs"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

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

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.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
name: SMI Traffic Specs
description: 'Traffic Specs describes a set of resources that allow users to specify how their

  traffic looks. It is used in concert with access control and other policies to

  concretely define what should happen to specific types of traffic as it flows

  through the mesh. Defines `HTTPRouteGroup`, `TCPRoute`, and `UDPRoute` resources.

  '
humanURL: https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-specs/v1alpha4/traffic-specs.md
aid: smi-traffic-specs
tags:
- Traffic Specs
- Routing
- HTTP
- TCP
- UDP
- Kubernetes CRD
- SMI
properties:
- type: APIVersion
  name: specs.smi-spec.io/v1alpha4
- type: Kind
  name: HTTPRouteGroup
- type: Kind
  name: TCPRoute
- type: Kind
  name: UDPRoute
- type: Specification
  url: https://github.com/servicemeshinterface/smi-spec/blob/main/apis/traffic-specs/v1alpha4/traffic-specs.md
- type: JSONSchema
  url: ./json-schema/http-route-group-schema.json
- type: JSONSchema
  url: ./json-schema/tcp-route-schema.json
- type: JSONSchema
  url: ./json-schema/udp-route-schema.json
- type: Examples
  url: ./examples/http-route-group-example.yaml
- type: Examples
  url: ./examples/tcp-route-example.yaml
- type: Examples
  url: ./examples/udp-route-example.yaml