API allowlists
Submit named Identity Addresses to customers and partners for independent access-policy review; approval is not guaranteed.
API Application
API Application
Public network identity for APIs, applications, and callbacks.
APIs and applications may need address evidence for allowlist requests, callback sources, webhook receivers, customer integrations, and security reviews. LARUS One can provide eligible endpoints named Identity Addresses and documentation for independent review; third-party acceptance is not guaranteed.
Identity capacity
One Identity Unit. Up to 254 globally unique Identity Addresses
Each LARUS One Identity Unit can activate up to 254 globally unique Identity Addresses at one deployed location, for the devices, endpoints, computers, servers, gateways, applications, APIs, and trusted access points that need stable public network identity.
The Identity Location is the selected home, office, family office, hotel, enterprise site, API edge, or private network where the Identity Unit is deployed through the LARUS One delivery network.
Actual usable count may depend on delivery design, security policy, and local network configuration.
Value
Give application traffic a documented address record
Use Identity Addresses for production APIs, internal APIs, webhooks, application callbacks, AI tool gateways, customer integrations, supplier systems, and partner access points.
Identity Address examples
Assign public network identity to the systems that need recognition
- Production API endpoint
- Webhook receiver
- Application callback gateway
- Internal API gateway
- AI tool gateway
- Customer integration endpoint
- Partner API access
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
AI-ready application access
Assign documented Identity Addresses to eligible AI tools, agent workflows, model gateways, and automation systems.
Evidence and rDNS
Name the identity and document it with Identity Passport and Allowlist Pack.
FAQ
Answers to common questions
Can webhooks and callbacks use Identity Addresses?
Yes. API endpoints, webhook receivers, and callback gateways can be assigned named Identity Addresses.
Can AI coding agents and API tools share this model?
Yes. AI coding tools, automation runners, and API gateways can use Identity Addresses from the same deployed Identity Unit.
Related use cases
Explore related ways to use network identity
Deploy
Deploy one Identity Unit to one selected location
Deploy one Identity Unit to one selected location and activate up to 254 globally unique Identity Addresses for the systems that need stable public network identity.
LARUS maintains the Identity Unit, Identity Addresses, Identity Passport, Allowlist Pack, and continuity record. The selected provider delivers the local network service.