NetBox API

Name: NetBox API
Brand: NetBox API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingbearer844 EndpointsREST

Install Jentic One Beta

Connect the NetBox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NetBox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetbox.dev%2Fnetbox-api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnetbox.dev%2Fnetbox-api" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NetBox API.

Allocate, reserve, and release IP addresses and prefixes through the IPAM endpoints

Inventory devices, racks, modules, and cables across one or many sites

Manage circuits and circuit terminations from upstream providers

GET STARTED

Start building with NetBox API

Explore with Jentic One

View OpenAPI Document

For Agents

Read and write infrastructure source-of-truth data in NetBox: devices, IPs, VLANs, circuits, racks, sites, and tenancy.

Use for: Allocate the next available IP address from a NetBox prefix, Register a new device in NetBox with site, rack, and role, List every circuit terminating at a given site, Find all VLANs assigned to a specific tenant

Not supported: Does not handle device configuration push, network monitoring, or DHCP issuance - use as a source-of-truth read and write API for network and data centre inventory only.

Use Cases

Patterns agents use NetBox API for, with concrete tasks.

★ Automated IP Allocation

Network engineering teams call /ipam/prefixes to pull the next available address when provisioning a device, then write it to /ipam/ip-addresses with the assigned object reference. The pattern replaces a shared spreadsheet with a queryable source of truth and keeps Terraform or Ansible runs idempotent.

Reserve the next available /32 from prefix 10.20.0.0/24 in NetBox and assign it to interface eth0 of device r1-edge.

Device Inventory Sync

Operations teams use /dcim/devices and the related rack and site endpoints to keep NetBox in sync with the physical environment. A scheduled job reads inventory from a network discovery tool, writes new devices to NetBox, updates serials, and reports drift so the next change request lands against accurate data.

Create a device named r1-edge in site dc-east, rack r-12, role edge-router, with the serial number ABC123.

Circuit and Provider Tracking

Network teams use the /circuits/ endpoints to record provider circuits and their terminations against sites and devices. The model captures circuit type, commit rate, and termination interface, so an outage on a provider circuit can be correlated to the affected sites without a separate tracker.

List all circuits terminating at site dc-east and return the provider name, circuit id, and commit rate for each.

AI Agent Integration via Jentic

An AI agent uses Jentic to query and update NetBox during a change workflow. Jentic exposes the dcim, ipam, circuits, and tenancy endpoints by intent, so an agent given a request to allocate an IP and add a device finds the right operations, supplies the model, and executes without hand-coding 844 endpoints.

Use Jentic to search for allocate next available ip in netbox, load the schema, and reserve the next /32 from prefix 10.20.0.0/24.

Key Endpoints

844 endpoints — jentic publishes the only available openapi specification for netbox api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/circuits/circuits/

List provider circuits

GET

/circuits/circuit-terminations/

List circuit terminations

GET

/circuits/circuit-types/

List circuit type definitions

GET

/circuits/provider-networks/

List provider networks

GET

/circuits/circuits/{id}/

Get a circuit by id

GET

/circuits/circuits/

List provider circuits

GET

/circuits/circuit-terminations/

List circuit terminations

GET

/circuits/circuit-types/

List circuit type definitions

GET

/circuits/provider-networks/

List provider networks

GET

/circuits/circuits/{id}/

Get a circuit by id

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the NetBox API by hand means passing the bearer token on every request and finding the right path among hundreds of circuit, device, and IP inventory endpoints against the host yourself. Through Jentic you install once, import NetBox from the API Directory, store the token once, and your agent calls it.

Permission scoping

NetBox puts the object id in the URL path (/circuits/circuits/{id}/), so a rule can pin your agent to reads for one circuit or inventory object and nothing else. You choose the operations it may call, so writes to other object types are not included unless you add them.

Credential isolation

Your NetBox bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'allocate an IP address in NetBox' or 'list circuits', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NetBox API through Jentic.

Why is there no official OpenAPI spec for NetBox API?

NetBox publishes a Swagger UI on every install but does not maintain a standards-validated OpenAPI 3.0 spec as a release artefact. Jentic generates and maintains this spec so AI agents and developers can call NetBox via structured tooling kept current with each release. Get started with Jentic One, the self-hosted execution layer.

What authentication does the NetBox API use?

NetBox uses bearer token authentication - generate a token in the NetBox UI under your user profile and pass it as Authorization: Token <key>. Jentic stores the token encrypted in your Jentic One instance so it is injected at execution time rather than passed through the agent context.

Can I allocate the next available IP from a NetBox prefix through the API?

Yes. The IPAM endpoints under /ipam/prefixes/ expose an available-ips action that returns the next free address inside a given prefix. Combine it with a write to /ipam/ip-addresses/ to allocate and assign the address atomically.

How do I list all devices at a site through Jentic?

Search Jentic for list netbox devices at a site, load the schema for the dcim devices endpoint, then execute with the site filter. The full flow is pip install jentic, search, load, execute.

What are the rate limits for the NetBox API?

NetBox does not impose API rate limits in the spec - limits depend on the operator's deployment. Treat large list calls as paginated and use brief=true for bulk reads to keep payload sizes small on heavily-populated installs.

Does this spec differ from the netbox.dev/main import?

No, the two imports cover the same NetBox 3.4 OpenAPI document - one was sourced from the JSON variant on apis.guru and the other from the YAML variant. Endpoint counts, paths, and methods are identical. Pick whichever matches your existing import path.

Can I limit what my agent is allowed to do with the NetBox API?

Yes. Jentic One is self-hosted by you, so your own rules decide which NetBox operations and credentials the agent may use. Because NetBox carries the object id in the URL path, such as /circuits/circuits/{id}/, you can pin the agent to reads of a single circuit, device, or IP object and nothing else. You choose the operations it may call, so writes to other object types like /dcim/devices/ or /ipam/ip-addresses/ are excluded unless you add them.