Scale by active Location, not by address count
People, devices, rooms, network segments, and workflows do not change the subscription count. Count the Locations used at the same time.
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.
USD 6,998 per Identity Unit-yearLocal delivery is separate from the LARUS One subscription.
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
Shared service model
Every use case follows the same commercial boundary
Identity, local delivery, and customer controls stay separate
LARUS anchors identity. The selected provider delivers the local network.
Evidence supports review; every third party decides its own acceptance policy
Identity Passport and Allowlist Pack evidence supports independent review. Every third party applies its own policy and decides access.
Customer controls
Public identity works with the customer security architecture. Firewalls, SASE, routing, segmentation, and access policies continue to control what is reachable.
From use case to paid pilot
Your first paid pilot
- 01
Start one paid pilot
Create an account and sign in to purchase one annual Identity Unit online.
- 02
Add the first Location
After purchase, add the office, property or other place where you will use the identity. Location profiles are free; one Unit serves one active Location at a time.
- 03
Arrange delivery and activate
Choose an available Certified Partner or an existing provider that supports BYOIP. LARUS and your provider confirm the delivery design and validate activation before you use the identity at that Location.
- 04
Review Identity Passport evidence
Review the Identity Passport and allowlist evidence, validate the workflow, then add one Unit for each additional active Location.
How LARUS One helps
LARUS anchors identity. The selected provider delivers the local network
API allowlists
Submit named Identity Addresses to customers and partners for independent access-policy review; approval is not guaranteed.
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.
One paid pilot
Choose one workflow and one Location to validate first
Confirm local delivery, routing, evidence, and reviewer fit before adding more active Locations.