AGNTCon + MCPCon North America · San Jose · Oct 22 to 23, 2026
Try the integration. Get a US$50 thank-you.
Eligible pilot participants receive a US$50 Amazon.com gift card for a genuine integration attempt and useful, honest feedback. Limited to 20 participants.
LoginID confirms eligibility and participation before you start. Success or a positive review is not required. Signing up alone does not earn a gift card.
Join the developer pilot
Registering records your interest so LoginID can follow up about access. It doesn't create an account, grant access or confirm you as a participant.
The registration form didn't load. Nothing was submitted. A browser extension or network filter may be blocking HubSpot.
This form asks for your email only. To tell us what you're building, use the project and feedback form.
Form not loading? Open it on HubSpot.
Pilot data notice. Your email is submitted directly to LoginID through HubSpot, the CRM LoginID uses, and stored there for follow-up about this event pilot. Project notes and feedback sent with the form further down are stored separately through Ploy. This is not a newsletter opt-in.
Questions: privacy@loginid.io. Full pilot notice
Add customer identity to your MCP server.
Connect agents to customer accounts with user-approved, scoped access.
Your service uses the customer's existing authorization system. Merchant access tokens stay server-side, out of the agent's context.
How it works in the docsStart with your coding agent
Open a coding agent in your project and paste this prompt. It follows the public quickstart to integrate LoginID AIGW (Agent Gateway) and asks you for the values it can't know. Review every change before you accept it.
Inspect this project’s existing MCP server and integrate LoginID AIGW using https://docs.testnet.loginid.io/mcp-ucp-integration/quickstart. Preserve existing authentication unless I approve changes. Ask for missing resource, issuer, token-endpoint, client-ID and scope settings; never guess them. Tell me which Console and merchant IAM steps I must complete. Keep secrets and merchant tokens server-side and out of chat. Implement the documented flow, run available checks, and report what passed and what remains blocked.
Test goal: a customer authorizes scoped access; your agent retries the MCP request; your server calls the backend without exposing the merchant token to the agent.
Before you build
- Access to an AIGW Evaluation Console account. Self-serve access isn't guaranteed, and registering pilot interest doesn't grant it.
- An MCP service you can change, and an admin for the merchant's identity and access management (IAM) system to work with.
- The correct resource, issuer, token endpoint, client ID and scope values for your setup.
- A backend to hold secrets. They never go in the agent, the browser or chat.
Docs status: an October 17, 2026 recheck confirmed discovery and client registration, then stopped at login. The code exchange and token redemption steps were not revalidated in that pass. See the quickstart note
What a customer connection looks like
A customer asks Muse for their Northwind orders. Three steps connect the agent to the customer's account.
-
Connect
Muse calls Northwind's MCP server. Without authorization, the server responds with a 401 that points Muse to LoginID AIGW.
-
Approve
The customer signs in with Northwind's own sign-in and approves read access to orders. Muse receives an AIGW token for this customer and this service.
-
Retry
Muse retries the request with the AIGW token. Northwind's server redeems it on the backend for Northwind's access token, which never reaches Muse.
Illustration with example values. Muse is Meta's personal agent; Northwind is a sample merchant.
Pilot details
Join the developer pilot- What does registering do?
- It records your interest so LoginID can follow up about access. It doesn't create an account, grant access or confirm you as a participant.
- Who receives the gift card?
- Up to 20 eligible participants. LoginID confirms eligibility and participation before you start, and the thank-you is for a genuine integration attempt with useful, honest feedback. Not everyone who registers receives one.
- How do you track progress?
- As three separate states: registered interest, an attempted integration you told us about, and a working flow LoginID verified with you directly. We don't infer any of them from page visits or telemetry.
- Do I need to register to read the docs?
- No. The docs, the agent prompt and the Evaluation Playground are open to everyone.
Need help or want to share what happened?
Ask a question, describe your project or tell us how your attempt went. It goes to the LoginID team running the pilot, and we reply by email.
This form is separate from pilot registration. Its submissions are stored through Ploy.
For failures, the step that broke, the error response and any request IDs help most. What to include
Pilot data notice
This notice covers the registration form and the project and feedback form on this page only.
The registration form asks for your email only. It is submitted directly to LoginID through HubSpot, the CRM LoginID uses, and stored there for follow-up about this event pilot.
The project and feedback form sends LoginID your email and your message. LoginID stores these submissions separately through Ploy, the platform that hosts this page. Ploy also records the page address and your IP address with each submission.
LoginID uses this information only to respond about pilot access, help with your integration and follow up on your feedback. Submitting either form is not a newsletter opt-in and doesn't subscribe you to marketing email.
Questions or requests about your pilot data: privacy@loginid.io. LoginID's general privacy policy covers LoginID's websites more broadly. For these forms, this notice describes what is collected.