Skip to content

Chyper Aperture ​

AI Gateway and Exchange solution on Chyper — AI Gateway, AI Exchange and AI distribution layer for providers, models, datasets, embeddings, vector stores, rerankers, prompt packs, memory packs, reasoning packs, evaluation packs, AI runtimes, agents, MCP/A2A, routing, guardrails, analytics and observability.

Chyper Aperture is the governed AI gateway and exchange for routing AI workloads across providers, models, datasets, embeddings, vector stores, rerankers, prompt packs, memory packs, reasoning packs, evaluation packs, AI runtimes, agents, MCP/A2A, guardrails, analytics and observability. Aperture does not distribute CyberLegion-owned solutions, apps, installers, licenses, deployments or updates. Those belong to one.cyberlegion.one. Aperture only connects AI workloads to AI providers, AI assets and AI runtime infrastructure.

Start with Aperture

Use your tenant account to open it, sign in, or request access. API calls use the same governed execution endpoint as the console.

API endpoint
POST https://api.dev.chyper.io/execute
Authorization: Bearer <YOUR_TENANT_API_TOKEN>
Content-Type: application/json

{
  "app": "<app id from this solution>",
  "input": {}
}

Apps In This Solution ​

Chyper Aperture groups 40 apps. Each app is a packaged capability your team uses through the console, in chat, or from the public API. Availability follows your tenant plan, roles, and permissions.

AppAreaWhat it does
A2A Gateway—Brokers agent-to-agent protocol endpoints with tenant policy and audit.
AgentPort—Routes agent endpoints, MCP servers, tools and workforce interfaces.
APIGateway—APIGateway for Aperture.
CanaryABRouting—CanaryABRouting for Aperture.
ConnectorPort—Routes AI ecosystem connectors without making them CyberLegion-owned products.
ContentModeration—ContentModeration for Aperture.
CostRoutingBudgets—CostRoutingBudgets for Aperture.
DataPort—Indexes, gates and routes datasets, eval sets and data products.
EgressSecurityAllowlist—EgressSecurityAllowlist for Aperture.
EmbeddingPort—Routes embedding models and embedding jobs across first-party, private and external providers.
EvalPacks—Publishes and routes evaluation suites, benchmarks and scoring packs.
FallbacksRetries—FallbacksRetries for Aperture.
GatewayAuditLog—GatewayAuditLog for Aperture.
GatewayObservability—GatewayObservability for Aperture.
GuardrailsPIIFilter—GuardrailsPIIFilter for Aperture.
KnowledgePort—Routes knowledge packs, retrieval sources and grounding assets for AI workloads.
LoadBalancing—LoadBalancing for Aperture.
MCPGateway—MCPGateway for Aperture.
MemoryPacks—Publishes and routes memory packs for agents and AI applications.
ModelComparePlayground—ModelComparePlayground for Aperture.
ModelPort—Routes and publishes model endpoints across first-party, private and external providers.
ModelRouter—ModelRouter for Aperture.
PromptManagement—PromptManagement for Aperture.
PromptPacks—Publishes and routes prompt packs for governed AI workflows.
ProviderKeyVault—ProviderKeyVault for Aperture.
ProviderRegistry—ProviderRegistry for Aperture.
RateLimitsQuotas—RateLimitsQuotas for Aperture.
ReasoningPacks—Publishes and routes reasoning patterns, chains and planner packs.
RerankPort—Routes reranker models and ranking jobs with latency, cost and quality controls.
RuntimePort—Routes AI runtimes, inference endpoints and execution backends.
SelfHostedDeploy—SelfHostedDeploy for Aperture.
SemanticCache—SemanticCache for Aperture.
SemanticRouter—SemanticRouter for Aperture.
StreamingProxy—StreamingProxy for Aperture.
TrainingPort—Routes training jobs and training providers through governed workload policy.
TunePort—Routes fine-tuning jobs, adapters and provider-specific tuning endpoints.
UsageMeteringBilling—UsageMeteringBilling for Aperture.
VectorPort—Routes vector stores, vector indexes and retrieval backends through governed provider policy.
VirtualKeys—VirtualKeys for Aperture.
WebhookGateway—WebhookGateway for Aperture.

How To Use It ​

ChannelBest for
ChatAsk for what you need in the Chyper console; the app plans, executes, and streams results back into your workspace history.
ConsoleOpen any app in this solution from the console, with your tenant's data, roles, and permissions applied.
APIAutomate an app from your own systems through the governed execution endpoint shown in the action panel above, using your tenant API token.

Every request is authenticated, authorized, and audited inside your tenant.

Tenant Safety ​

  • Public docs never show tenant records, identifiers, private URLs, credentials, or configuration.
  • Apps render only the data your tenant returns; empty states stay empty.
  • Keep API tokens in your own vault or runtime environment. Never paste them into docs, tickets, or support requests.

Need help?

Use the Support action above, or browse the app catalog.