How to Try SecureAuth or Get Pricing for Its Agent Authority Platform

SecureAuth's site exposes two direct commercial paths: a Pricing page at secureauth.com/pricing, and a "free trial" signal on the site. If you want to evaluate Agent Authority before committing, start with the pricing page for packaging and commercial terms, and use the trial entry to test discovery, delegated access tracing, and runtime enforcement against your own agents. The site does not publish specific price points, tiers, or trial length in the material available, so treat any figure you see elsewhere as unverified until confirmed by SecureAuth directly.

What you can do on the site today

The pricing page is the authoritative place to check current packaging. Because pricing signals on the site are limited to the page link and a "free trial" keyword, do not assume a self-serve checkout, a published per-agent rate, or a no-login trial — none of that is confirmed in the available material.

What you are actually evaluating

Before you ask for a quote, it helps to know what the platform claims to do, because that shapes which questions to ask on a trial or demo call.

Discovery and agent topology

Agent Authority is positioned to discover agents and non-human identities (NHIs) in real time — which agents run, the identities they use, and the tools they reach. The platform presents this as an agent topology graph covering teams, their agents, the policies that decide their calls, and the MCP servers they reach.

Delegated access tracing

The platform traces who authorized each agent, how far that authority reaches, and where it was used. This matters because, per SecureAuth's framing, agents get access once and then act across applications, data, and workflows — some delegated by an employee, some running as service accounts, some acting on their own.

Runtime enforcement

Every agent action is evaluated against policy, risk, and context before the agent can act. The decision set is: Allow, Deny, Redact, Throttle, Escalate, or Human approval. Data redaction happens before data reaches the agent.

Policy readability and blast radius

Access policies are described as readable and configurable by agent, user, group, tool, and condition, with the blast radius shown before you save.

Questions to bring to a trial or pricing conversation

Use these to convert a generic demo into a decision:

1. Scope of discovery — Does it find agents across all the identity types we run (delegated, service account, autonomous)?
2. Enforcement point — Where does the runtime decision sit relative to our MCP servers and internal tools?
3. Redaction depth — Which data classes can be redacted before the agent sees them?
4. Policy authoring — Can a non-engineer read and safely edit a policy, given the blast-radius preview?
5. Commercial model — Is pricing per agent, per identity, per action volume, or per seat? (Not published on the site — ask directly.)
6. Trial terms — Length, environment (sandbox vs. production), and what data you need to connect.

Practical path

• Step 1: Open secureauth.com/pricing to see current plan structure and request a quote.
• Step 2: Use the free trial entry to stand up discovery in a limited environment and confirm what the platform actually sees.
• Step 3: Test one enforcement decision end to end — pick a policy, trigger an agent action, and verify the Allow/Deny/Redact outcome.
• Step 4: Bring the six questions above to the commercial conversation so pricing maps to your real agent and identity count.

Expected result: you leave with a confirmed quote basis and evidence that discovery, tracing, and enforcement work on your agents — not just on a vendor demo tenant.

Common snag: teams often start with enforcement before discovery, so they cannot tell which agent triggered a denial. Run discovery first; the topology graph is what makes every later decision explainable.