CSV, XLSX, XLSM, DOCX and PDF · Multiple files become one RFP project · Agents process each document
Import from Google Doc
The document must be shared with your Google account (authenticated via Google MCP).
⏳
Loading…
Knowledge Base
Loading…
Loading knowledge base…
Agent Architecture
7 specialized AI agents collaborating to process RFPs autonomously
Pipeline Flow
Agent Details — Click any card
Demo Library
Confirmed demo plans — ready to use
⏳
Loading…
Discover RFPs
Open Canadian public sector tenders — identity and AI security
🔍
No results yet
Click Run Discovery to search Canadian procurement portals.
Settings
Configure your API key and integrations
No API key configured
Your key is stored locally in the SQLite database — never sent anywhere except Anthropic's API.
Your Okta LiteLLM proxy. Leave blank to call Anthropic directly.
When enabled, agents fetch live data from trust.okta.com and docs.okta.com. Disable for faster processing — KB has 640+ entries from the SIG.
Used to identify your RFP source folder in Drive. Manual import not yet implemented — use file upload for now.
⚠
Authentication is disabled for hackathon judging.
NaughtRFP is designed to authenticate SEs via Okta OIDC (Authorization Code + PKCE). The full auth flow — login, token validation, session management, and logout — is implemented but bypassed so judges can access the app without an Okta account. To enable for production, configure your Okta domain and Client ID below, then toggle Enable Okta Authentication on.
Okta Domain
Your Okta org URL (e.g. https://okta.okta.com)
Client ID
OIDC app client ID from the Okta Admin Console
Redirect URI
Must match the redirect URI configured in the Okta OIDC app
When enabled, all routes require a valid Okta session. Users are redirected to Okta login via OIDC Authorization Code + PKCE flow. Leave disabled for judge access.