Agent Access AI

A coming-soon standalone paid WordPress access product with secure Google identity, deterministic domain policies, safe post-login routes and a human-approved AI roadmap.

Description

Paid / in development
Let AI explain the route. Let the server guard the door.

Make sign-in, access rules and the first route after login feel like one coherent product

Agent Access AI is a standalone commercial plugin for authentication, server-authoritative domain policies, safe post-login routing and future personalised onboarding.

The 0.1.1 development foundation already contains secure Google OAuth with PKCE, optional domain allow or block lists, several local routes, eight button styles and a careful migration path from Agent Google Login Free.

Agent Access AI verifies user identities through a deterministic shield and routes them to safe local WordPress destinations

The routine that quietly grows with the site

Small sites need a safe front door, not an enterprise identity contract that grows a new monthly invoice every quarter

Login, access policy and onboarding often become separate services with separate dashboards. We are building one owned WordPress product where deterministic server rules keep working even when every future AI provider is offline.

Affordable, effortless and beginner-friendly

01

Google identity foundation

OAuth 2.0 Authorization Code with PKCE, one-time state and issuer, audience, expiry and verified-email checks.

02

Predictable local policy

Optional e-mail-domain allow and block lists make the final access decision on the WordPress server.

03

Safe routes after login

Choose requested, smart, home, dashboard, WooCommerce account or a validated custom-local destination.

A short workflow on purpose

Connect Google -> set the deterministic policy -> choose a local destination

1

Create the identity route

Add a Google Web OAuth credential and copy the exact redirect URI from WordPress.

2

Define access clearly

Use local allow or block rules while leaving the final sign-in decision independent of AI availability.

3

Guide the next step

Choose a safe local route after login and later add a human-approved onboarding scenario.

Where it saves the most attention

  • A membership site routing different approved users to the right local account area.
  • A private team site allowing or blocking entire e-mail domains with deterministic rules.
  • A WooCommerce site offering a familiar sign-in and a direct account destination.
  • A beginner who wants one owned access product instead of several recurring identity add-ons.
What you need to start

  • WordPress 6.0 or newer and PHP 7.4 or newer.
  • A Google Cloud Web OAuth Client ID and Client Secret for the current identity adapter.
  • The exact plugin redirect URI authorised in Google Cloud and a real HTTPS site for production use.
  • The present 0.1.1 development foundation must pass the documented 1.0 gates before production sale or deployment.
Official provider setup and policies

Use Google's official setup, identity and policy pages for the current working adapter

The current development interface shows only the identity provider with a working adapter: Google. Future Microsoft or Apple options will appear only after their adapters and configuration tests exist.

An honest deal instead of a subscription maze

We are a small product workshop. We do not need to turn every useful button into a monthly bill

Similar products probably exist. Before choosing one, ask a simple question: can you keep using the useful part without another mandatory monthly payment?

Product status: Coming soon. Version 0.1.1 is a pre-release development foundation. Google identity and local policy are implemented, while the broader provider, onboarding and AI milestones remain ahead.

When the release gates pass and sales open, the AgentWP licence will follow one plain principle: pay once and own the product you bought. No mandatory monthly AgentWP subscription.

If a future Pro feature uses an external AI or data provider, that provider’s price and terms will be disclosed separately before purchase — never hidden inside the AgentWP licence.

If you want more later

It could draft access and onboarding rules in ordinary language when paired with the future confirmed AI module

The planned assistant would return a structured draft, show a before-and-after diff and wait for human confirmation. The server would still validate the allowlisted rule and remain the final authority.

Control remains visible

AI may advise later; it will never become the final gatekeeper for a WordPress session

OAuth secrets, raw tokens and private profiles stay out of HTML and diagnostic logs. Redirects must remain local, domain policy works without AI, and third-party login connectors are detected rather than silently disabled.

Paid / Coming soon

Own the access workflow while keeping every final security decision deterministic

Coming soon after the independent plugin reaches its full release gate. Google service terms remain separate; the AgentWP product itself is planned as a one-time purchase.

Coming soon – checkout stays closed until release

Catalog preview: no price, checkout or download is active yet.

Ask a question
AI Assistant↔ drag
0 / 1500