New Powered by MB License Management

Secure every API call.
Control every license.

One secure entry point for authentication, licensing, policy enforcement, routing and observability across your WordPress plugins, SaaS products and internal services.

  • No upstream secrets in client code
  • License-aware access control
  • Centralized audit trail
Signed policy Live observability Version-aware routing
Gateway Control Plane Policy · Routing · Observability
Live
api.trangpc.vn/v1/gateway
TLS
POST /v1/gateway/request
Operational
// Client sends license context, never provider secrets
{
  "license_key": "MBL-••••-••••-4A7F",
  "service": "trangpc-ai",
  "action": "generate",
  "client": {
    "app": "wordpress",
    "version": "1.4.0",
    "env": "production"
  }
}
Policy approved Active license · Pro entitlement · Signature valid
200 OK
42 msedge latency 4,820requests 100%audited
Policy latency < 50 ms
Security layer Always enforced

One policy plane across the TrangPC ecosystem

WordPress Plugins Distributed clients AI Services Protected inference MB License Entitlement source Internal APIs Private services SaaS Products Tenant-aware access
01

99.95 %

Availability target

Design goal for the policy plane

02

< 50 ms

Policy decision budget

Overhead added before routing

03

100 %

Decisions audited

Every allow, deny and throttle

04

0

Secrets in client code

Upstream credentials stay server-side

Figures describe design targets for the platform, not measured production results. Replace them with your own verified numbers before launch.

Gateway capabilities

Built for secure API delivery,
not just request forwarding.

Move sensitive decisions out of distributed client code and into a centralized boundary designed around licensing, access policy and operational visibility.

Routing

Smart API routing

Route by service, API version, environment, tenant, entitlement or current license state — and change any of it without redeploying a single client.

Identity

Central authentication

API keys, license keys, request signatures and access decisions live behind one consistent control point instead of being scattered across every consumer.

Usage

Quota enforcement

Apply request limits by plan, customer, service, feature entitlement or billing period.

Protection

Rate limiting

Absorb bursts and reduce abuse before suspicious traffic ever reaches a protected upstream service.

Lifecycle

Versioned contracts

Run several API versions side by side and migrate consumers on their own schedule.

Isolation

Secrets stay server-side

Upstream URLs, provider tokens and internal routing rules never ship inside a distributable plugin package.

Observability

Audit every decision

Request IDs, policy outcomes, response codes and latency are recorded together, so operations teams investigate with evidence instead of guesses.

MB License Management

Turn licensing into a real-time API policy.

A valid activation is only the beginning. The gateway evaluates license status, entitlements, environment, client scope and usage policy before every protected operation.

01

Identify the client

The plugin or application sends its license context, client identity, requested service and request metadata — nothing else.

Client ID Environment License key
02

Evaluate MB License policy

Activation status, entitlement, allowed scope, remaining quota and security conditions are checked together before access is granted.

Active Pro entitlement Signature valid Quota available
03

Route only approved traffic

Compliant requests continue to the protected service. Everything else stops at the policy boundary and is recorded with a reason.

Allow Throttle Deny Audit

See the integration flow

Security by design

Keep secrets server-side.
Decide access at the edge.

This page presents a security-first architecture without pretending that a user interface secures an API. Real enforcement lives in the gateway and the MB License Management backend.

Request assessment

Policy decision

Low risk
  • License active Activation and entitlement are valid.
  • Client allowed Application sits inside the licensed scope.
  • Quota available The current plan still has request capacity.
  • Request trusted Signature and timestamp satisfy policy.
  • Request signing

    Signatures and timestamps strengthen trust between supported clients and the gateway.

  • Key rotation

    Rotate server-side credentials without shipping a new secret to every installed client.

  • Replay protection

    Reject stale or previously accepted signed requests when your policy requires it.

  • Adaptive limits

    Combine per-license quotas with rate limits to protect expensive upstream workloads.

  • Audit trail

    Every policy decision carries a request identifier for review and incident analysis.

  • Minimal exposure

    Upstream URLs, provider tokens and routing logic stay out of distributable code.

Developer experience

One endpoint for the client.
One place to enforce policy.

Your distributed plugins and applications call TrangPC API Gateway. Provider credentials and licensing decisions never leave the server.

  • Stable client contract Evolve internal services freely without exposing their topology to anyone downstream.
  • Central policy changes Update limits and entitlements once, without redeploying every consumer.
  • Clear failure states Consistent auth, quota, validation and service errors that clients can act on.
Quick start
Server-side
# Example contract — replace with your production endpoint
curl -X POST https://api.trangpc.vn/v1/request \
  -H "Content-Type: application/json" \
  -H "X-License-Key: $TRANGPC_LICENSE_KEY" \
  -H "X-Client-Id: $TRANGPC_CLIENT_ID" \
  -d '{
    "service": "trangpc-ai",
    "action": "generate",
    "payload": { "prompt": "Hello TrangPC" }
  }'

Presentation example. The endpoint, headers and payload above illustrate the integration shape. They are not a claim about your current live API contract — publish your verified contract before customers build against it.

Use cases

One gateway across every product you ship.

Standardize how different products reach protected capabilities while preserving the entitlements that make each product distinct.

WordPress plugins

Reach AI, update, content and private services from a plugin you ship publicly, without embedding upstream credentials in the package.

Integration pattern

SaaS products

Evaluate access by tenant, plan, entitlement, usage quota and environment before any protected operation runs.

Licensing model

AI services

Hide provider credentials behind one controlled API and apply per-license limits around expensive inference workloads.

Security model
License tiers

Entitlements that match how you ship.

Every tier is enforced by the same policy engine. What changes is scope, quota and the depth of the security controls available to you.

Starter

For a single product or a first integration behind the gateway.

Single environment One activation scope per license

  • License validation per request
  • Baseline rate limiting
  • Standard routing rules
  • Request audit log
Start integration

Enterprise

For teams with custom policy, compliance or isolation requirements.

Custom deployment Dedicated or self-hosted policy plane

  • Everything in Professional
  • Custom policy rules
  • Private routing topology
  • Key rotation workflows
  • Priority incident support
Contact sales

Tier contents describe entitlement scope, not a published price list. Confirm commercial terms before you rely on them.

Frequently asked

What developers ask first.

Straight answers about the role of the gateway, MB License Management and this presentation layer.

How is TrangPC API Gateway different from calling an upstream API directly?
The gateway introduces a controlled boundary. Authentication, licensing, quota, rate-limit, audit and routing decisions all happen before a request reaches a protected service, instead of being duplicated across every client.
Where does MB License Management fit?
MB License Management is the licensing and entitlement source of truth. The gateway reads its validated state and policy information to decide whether a client may reach a protected capability.
Is this architecture suitable for distributed WordPress plugins?
Yes, and that is its strongest use case. A plugin you ship to customers can call protected services without embedding upstream provider keys or internal routing details in code that anyone can read.
Does this WordPress theme itself secure the API?
No. This theme is the public presentation layer only. Authentication, signature verification, rate limiting, license validation and secret management must be implemented in the gateway and licensing backend.
Are the endpoints and numbers shown on this page live production values?
No. Endpoint names, sample payloads, latency figures and policy responses on this page are interface examples. Replace them with your verified production contract and measured numbers before publishing.
Can the gateway sit in front of services we did not build?
That is the usual pattern. Third-party AI providers, billing systems and internal microservices can all sit behind one boundary, so provider credentials stay server-side and limits are applied consistently.
TrangPC Developer Platform

Build on one secure API boundary.

Centralize access control, licensing policy and service routing without exposing your internal architecture to every client you ship.