F5 Load Balancer
APIs for managing F5 BIG-IP Load Balancer configuration, monitoring, and operations. F5 BIG-IP is an application delivery controller that provides intelligent traffic management, load balancing, and application security.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles F5 Load Balancer the way a machine reads it — 27 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — F5 Load Balancer scores 50.5/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile F5 Load Balancer
Each block below is one kind of artifact we hold for F5 Load Balancer. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
F5 Load Balancer Config API
Retrieve the original device configuration before Declarative Onboarding modifications were applied.
F5 Load Balancer Data Groups API
Manage internal and external data groups used for address, string, and integer lookups in traffic processing decisions.
F5 Load Balancer Declarations API
Submit, retrieve, and manage AS3 declarations that describe the desired application services configuration state on the BIG-IP system.
F5 Load Balancer Info API
Retrieve version and capability information about the installed AS3 extension.
F5 Load Balancer Inspect API
Inspect the current state of BIG-IP configuration classes known to Declarative Onboarding.
F5 Load Balancer iRules API
Manage iRules for custom traffic management logic using the F5 Tcl-based scripting language.
F5 Load Balancer Monitors API
Configure health monitors that verify the availability and performance of nodes, pool members, and services.
F5 Load Balancer Nodes API
Manage backend server nodes identified by IP address or FQDN that serve as the foundation for pool member definitions.
F5 Load Balancer Policies API
Manage local traffic policies that provide rule-based traffic steering and content manipulation capabilities.
F5 Load Balancer Pool Members API
Manage individual server members within load balancing pools including their state, ratio, priority group, and connection limits.
F5 Load Balancer Pools API
Manage pools of backend servers for load distribution and health monitoring.
F5 Load Balancer Profiles API
Manage traffic profiles that define how the BIG-IP processes different types of network traffic including HTTP, TCP, SSL, and persistence.
F5 Load Balancer SNAT Pools API
Manage SNAT (Secure Network Address Translation) pools that define translation addresses for outbound connections.
F5 Load Balancer SSL Certificates API
Manage SSL certificates and keys used for TLS/SSL termination and re-encryption on virtual servers.
F5 Load Balancer System API
Access system-level information and configuration including device status, software versions, and global settings.
F5 Load Balancer Tasks API
Monitor the status of asynchronous declaration processing tasks.
F5 Load Balancer Virtual Servers API
Manage virtual servers that direct client traffic to appropriate server pools based on configured rules and profiles.
Scroll within the panel for all 17 ·
Open Collections 3
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
F5 Load Balancer F5 BIG-IP Declarative Onboarding (DO) API
OPEN COLLECTIONF5 Load Balancer F5 BIG-IP iControl REST API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
F5 Load Balancer Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
F5 Load Balancer Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for F5 Load Balancer — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/f5-load-balancer · machine-readable index on apis.io