Concepts & Glossary
Use this section to connect Noxtica terminology to an operating decision. Each concept explains the problem it addresses, where it appears in the product or API, the output your team receives, and the boundary of what that output can establish.
Noxtica separates intelligence from action. The intelligence layer describes a browser, device, network context, or verified agent claim. Your application and configured policies decide whether to allow, observe, step up, or block. The AI Assistant and MCP integration are read-only ways to investigate that tenant-scoped information; neither is an autonomous control plane.
The Intelligence pillar
Use the intelligence concepts when you need evidence about traffic before changing the customer journey.
- Know Your Device (KYD) — turns a browser assessment into a site-scoped identifier, risk score, risk level, confidence, and flags that your application can store and review.
- Know Your Agent (KYA) — where provisioned, compares cryptographically presented agent identity with the trust policy for your tenant. It does not grant an agent authority.
- Browser Intelligence — explains the categories of browser and edge context that contribute to an assessment, and how to consume the result through the SDK, console, or Server API.
These outputs support fraud review, account protection, signup controls, abuse investigation, and traffic analysis. They are risk evidence, not proof of a person’s identity or intent.
The Security pillar
Use the security concept after your team has decided what each level of risk should mean for a particular route or transaction.
- Browser Security — applies customer-owned policy to intelligence outputs. Your application can act on API results directly; eligible tenants may also use configured risk-action controls and shadow mode.
Keep collection and enforcement separate during rollout. Observe the output on representative traffic, choose thresholds for each surface, and only then introduce customer friction.
The Agentic spine
“Agentic” describes three different customer workflows. It does not mean that Noxtica autonomously changes your systems.
- Agentic Security — the umbrella for investigating with the assistant, connecting read-only external agents through MCP, and governing incoming automated agents.
- MCP Integration — an opt-in, tenant-scoped, read-only MCP surface for eligible tenants. External agents can retrieve allowed Noxtica context but cannot modify it.
- AI Assistant — a console-based operator assistant that reads only what the signed-in operator is permitted to read and returns summaries for human review.
- Know Your Agent (KYA) — a separate defensive capability for evaluating agents that reach your application; availability and supported identity paths depend on provisioning.
Calibration
- Calibration — explains how to use the score, risk level, confidence, and flags together instead of treating any one field as a binary verdict.
Calibration matters when the cost of a false positive differs by workflow. A medium-risk signup, a high-value payment, and a public read-only route can use the same assessment differently because your policy owns the consequence.
Start with your task
| If you need to… | Start here | Continue with |
|---|---|---|
| Add browser assessment to a site | Browser Intelligence | Getting started |
| Use an identifier or risk result in backend logic | Know Your Device | Backend integration |
| Choose risk thresholds and customer treatment | Calibration | Features: risk and decisioning |
| Observe, challenge, or block by policy | Browser Security | Integration flow: decision |
| Investigate tenant state in the console | AI Assistant | Features: AI-assisted operations |
| Let an external agent read approved context | MCP Integration | Features: AI-assisted operations |
| Evaluate incoming automated agents | Know Your Agent | Agentic Security |
Availability and scope
Browser collection, its returned fields, and server-side device lookup are documented in the public integration guides. Assistant access, MCP, KYA, managed enforcement, and native mobile capabilities can depend on plan, tenant provisioning, and supported deployment context. Confirm those capabilities for your tenant before making them a launch dependency. The browser concepts do not imply that native mobile attestation is included.
Related reading
- Features reference — customer-visible capabilities and where they appear.
- Getting started — install the browser collector and receive a result.
- Backend integration — look up device risk and use it in server-side policy.
- Engineering principles — the operating constraints behind every surface.
- Why calibration, not verdicts — the decision model behind the platform.
- Detection signals — the evidence categories behind browser assessment.
- Integration flow — browser collection to customer-owned decision, end to end.