Friday F.ai

About Friday F.ai

Friday F.ai is an AI platform by Zylink Corp, a Nigerian enterprise-technology group headquartered in Port Harcourt, Rivers State. Friday is built for individuals, developers, and enterprises that want a single intelligent assistant which knows them, adapts to their industry, and acts on their connected apps — not just answers questions.

The whole system runs behind a Cloudflare Workers gateway that keeps every upstream API key server-side. Users authenticate with scoped fri_ keys; per-user connector tokens are encrypted at rest with AES-GCM keys derived per-user from a worker secret.

What's new in v4.3

v3.3 — May 2026

Earlier releases

Features

Products inside Friday

AI Models

Friday routes to the best model based on your request. Switch modes manually with the pill inside the chat input bar.

Pro and Max get smarter the more provider keys you configure — they call every available brain in parallel and fuse the results into one best answer.

Multi-turn conversation history

The worker now accepts a role-tagged history array on every request, so Friday holds the conversation across turns at the model level rather than reconstructing it from a flattened string. Capped at 20 turns × 8 K characters.

Auto-routing

In Default mode, Friday detects current-sounding questions (containing words like today, latest, 2026, news, price, weather) and switches to Browse mode transparently. Code questions are excluded from auto-switching. A ✨ Auto-switched to Browse badge appears when this happens.

Tavily RAG on Default

If a Tavily API key is configured, Default mode enriches every response with live web search results injected into a delimited <<<USER_QUERY>>> block so prompt-injection from search payloads is contained.

Memory & Intelligence

Friday builds a personal memory profile for every signed-in user that persists across all conversations and devices.

Image Generation

Friday detects image requests in natural language and generates with Friday's image engine behind the worker. Style picker appears before render so you can choose Flux, Turbo, Realistic, Anime, Logo, 3D, or Dark Art.

How to trigger

"generate an image of…", "draw me a…", "create a picture of…", "paint a…", "illustrate…", "imagine…"

Rate-limit responses (429/503/500) include a retry: true signal with a recommended wait; the browser retries up to 5 times cycling through turbo → flux → any-dark before giving up. The retry loop runs client-side so Cloudflare's 30s CPU limit is never approached.

Industry Personas

Friday adapts its behaviour and language to your industry. Set yours in Settings → Personalise Friday. The intelligence layer also detects domain mid-conversation and injects extra context automatically.

Each persona carries domain jargon, regional context (Nigerian where applicable), and behaviour rules — Mental Health, for example, never diagnoses and always points to qualified professionals + crisis hotlines.

Connectors

30+ integrations browsable in connector-dashboard.html. The 9 live ones below execute real actions on your apps from chat — the rest store credentials and are pending adapter implementation. All sensitive fields are AES-GCM encrypted at rest with per-user keys derived from a worker secret.

Live — chat-driven actions

Apps Script integrations (pull-based)

Drop a generated Apps Script into Sheets, Gmail, Docs, Forms, Slides, Drive, Calendar, or Sites — and Friday adds a custom menu / on-edit triggers that call the worker on demand. Generated by generateAppsScript(type, …) in friday-intelligence.js.

OAuth + dashboard-only (no chat actions yet)

The dashboard supports 20+ more integrations — Apple Music, Instagram, X/Twitter, LinkedIn, TikTok, Discord, Airtable, Asana, Zoom, Dropbox, Mailchimp, Microsoft Teams, Jira, Paystack, Flutterwave, WhatsApp, Webhook, Zapier, Make, Zino (internal). Credentials are stored encrypted; adapter implementations land case-by-case.

Custom outbound webhook

Configure a webhook URL in the dashboard and Friday will POST every chat response to it in real time:

Google Workspace

Single click — sign in with Google and Friday gets access to Gmail, Calendar, Drive, and Tasks. Tokens are stored encrypted; refresh happens automatically. Configure the operator's OAuth client via GOOGLE_CLIENT_ID + GOOGLE_CLIENT_SECRET on the worker.

Higher-level automations

Dashboard

The Dashboard gives real-time visibility into all API key activity, plus per-bot analytics for any bots you've published with the Bot Builder.

Usage is logged via ctx.waitUntil to usage_logs in Firestore — fire-and-forget but guaranteed to complete. Each log records key, model, industry, timestamp, prompt length, reply length, and whether the response was grounded.

API & Developer Keys

Generate scoped fri_ keys in developers.html. Each key stores a name, system prompt, and model routing preference in Firestore and is validated on every gateway request.

Gateway endpoint

Response format

Health check

Image generation

Other endpoints

• connector_save · connector_action · connector_call · connector_test · connector_disconnect — encrypted credential storage + live execution against connected apps
• oauth_exchange — server-side code-for-token exchange for Spotify and Google (refresh-token aware)
• morning_brief · meeting_agent · crm_lite_run · drive_kb · compliance_check — Google Workspace automations
• bot_save · bot_log · bot_stats · bot_list · bot_delete · bot_telegram_deploy — Bot Builder hosting + telemetry
• kb_url_fetch — server-side URL scrape for the Bot Builder knowledge base
• GET /b/{slug} — public bot serving (rendered HTML)
• POST /webhook/telegram/{prefix} — Telegram bot inbound webhook

v3.3 additions

• POST /stream/chat — Server-Sent Events token streaming with mid-stream steer
• POST /async/submit · /async/status · /async/list · /async/cancel — fire-and-forget background jobs
• POST /push/subscribe · /push/notify — Web Push fan-out
• type:'vision' — multimodal image+text
• type:'megamind' — multi-provider router with key-pool rotation (many AI brains)
• type:'fact_check' — claim verification with source caching
• type:'fx_rate' — currency conversion with 6h cache
• type:'naija_news' — RSS aggregator + AI digest across 12 Nigerian outlets
• type:'naija_jobs' — cross-source job scraping + cover-letter generation
• Daily-brief scheduled() — fires morning/midday/evening/night briefs per user-configured local time
• 5 new connector adapters: Paystack · Flutterwave · Monnify · Airtime (routed via any connected payment provider) · Identity (VerifyMe / YouVerify for BVN/NIN/passport/driver's licence)

v4.2 additions

• model:'pro' & model:'max' — the council/ensemble routes that fan out to every configured provider and fuse the answers
• type:'deep_research' — plan sub-queries → multi-source search → one cited report
• type:'transcribe' — audio chunk → text (powers the Meeting Notetaker)
• type:'video_render' · 'video_status' — studio-quality cloud video (json2video), submit + poll
• type:'tts' — free text-to-speech (Imgen narration)
• type:'imgen_animate' — best-effort free text-to-video clips for Imgen
• type:'whatsapp_config' · 'whatsapp_get' + GET/POST /webhook/whatsapp — the WhatsApp business agent
• Web-grounded replies now return a sources array (rendered as tappable source pills in the app)
• Per-request intelligence directive powers Direct answers mode and the personalised Friday Live voice

v5 additions — Friday Agent + Clid Cloud native auth

• type:'agent' & POST /stream/agent — the autonomous, tool-calling Friday Agent (a Z.ai-GLM-style loop: plan → call tools → observe results → continue up to 8 turns). Tools: web_search, fetch_url, calculator, code_exec, image_gen, generate_api_key, translate, send_email, list_calendar_events.
• type:'agent_key_gen' · 'agent_key_list' · 'agent_key_revoke' — mint, list, and revoke fri_agent_ API keys. Each key grants access to the Friday Agent API and lasts 1 year by default.
• Clid Cloud native auth — Friday accepts clidkey_... API keys, clid_live_... keys, Clid session JWTs, AND raw Clid worker session tokens (base64url 30-64 chars) directly. The worker calls GET /api/cloud/me on the Clid Cloud worker to validate, then derives a stable per-account uid.
• Clid Storage mirror — when authenticated via Clid, per-user data (minted agent keys, audit logs) is mirrored to Clid Storage instead of Firestore.
• Full API reference — see the new Friday Agent API Reference section below for complete endpoint specs, all 9 tools with request/response examples, auth methods, code samples in curl / JavaScript / Python, and the Clid Cloud Vortex Fade integration.

Friday Agent — Autonomous Tool-Calling

The Friday Agent is an autonomous, tool-using AI agent — exactly like Z.ai GLM, Claude Code, or ChatGPT with tools. It plans, calls tools, observes results, then continues until your request is fully satisfied. Up to 8 reasoning turns per request, with a 14,000-character tool-result budget.

Try it from the Clid Cloud dashboard

Sign in at cloud-6pp.pages.dev/dashboard.html#/vortex-fade, pick a project with the Vortex Fade module enabled, and start chatting. The agent streams live tokens, tool-call cards, and tool results as it works.

Gateway endpoints

Streaming (SSE)

Mint your own API key

Send any of these prompts to the agent and it will call its generate_api_key tool, returning a fresh fri_agent_... key in the chat:

• "please generate an api key for me"
• "generate an api key"
• "mint an api key labelled dev-laptop"
• "i need an api key"

Or call the type directly:

List & revoke keys

Available tools

• web_search(query, max_results=5) — live web search via Tavily
• fetch_url(url) — fetch + clean a web page (max ~8k chars)
• calculator(expression) — safe math eval (sqrt, sin, cos, log, …)
• code_exec(language='javascript', code) — sandboxed JS eval (5s timeout, no fs/network)
• image_gen(prompt, width=1024, height=1024, style='realistic') — Pollinations image gen (realistic / photo / art / anime / logo / cinematic / 3d / turbo)
• generate_api_key(label='') — mint a fri_agent_ key for the caller
• translate(text, target_lang) — translate into any language
• send_email(to, subject, body) — send via connected Gmail
• list_calendar_events(days=7) — list upcoming Google Calendar events

Vortex Fade — on Clid Cloud

The Friday Agent is also reachable through the Clid Cloud worker, which adds project-scoped access control + audit logging. These endpoints accept a Clid Cloud API key (clidkey_...) or Clid session JWT:

The Vortex Fade module must be enabled on the target project (it's listed in enabled_modules). Enable it from Clid Cloud → Modules → Vortex Fade → Enable.

v6 — Chat History via Clid Storage + Service Binding

Friday chat history now lives in Clid Storage for Clid-authenticated users. Legacy fri_ keys keep using the Firebase SDK directly — the migration is opt-in: a user switches to a Clid key when they're ready, and from that point their chat history lives on their Clid Cloud account.

v6 additions

• Per-user chat history routes — /api/conversations* + /api/memory/profile. Backed by Clid Storage under friday/<uid>/conversations.json, friday/<uid>/conv/<convId>.json, friday/<uid>/memory/profile.json.
• Clid Cloud service binding — the Friday worker now calls the cloud worker via env.CLOUD.fetch() (a Cloudflare service binding) instead of fetch('https://cloud.zylink-corp.workers.dev/...'). This bypasses Cloudflare error 1042 ("Worker tried to call itself") which occurs when two workers on the same account call each other via HTTP. The service binding routes through Cloudflare's internal service mesh — no HTTP round-trip, sub-ms latency.
• Dual key-prefix support — both clidkey_... (OAuth API keys from Clid Auth) and clid_live_... (cloud-internal API keys from POST /api/cloud/keys) are accepted. Both validate against GET /api/cloud/me on the cloud worker.
• CORS fix — Access-Control-Allow-Headers now includes Authorization so browser-based clients (the migration tool, the chat UI) can send Authorization: Bearer clid_live_... without "Failed to fetch" errors.

Chat history routes

All routes require Authorization: Bearer <fridayKey> where fridayKey is a clidkey_... or clid_live_... key. The worker resolves your uid via validateFridayKey → validateClidToken → GET /api/cloud/me.

Clid auth migration guide

If you're an existing Friday user with chat history in Firebase, you can migrate it to Clid Storage in one click:

1. Sign in to Friday chat (Firebase auth)
2. Sign in to Clid Cloud dashboard (Clid auth)
3. Mint a Clid API key at Clid Cloud → API Keys with storage:read + storage:write scopes
4. Open the migration tool — it auto-detects your Clid key from localStorage
5. Click "Dry run" to preview, then "Start migration"

After migration, set localStorage.setItem('friday_pub_key', 'clid_live_...') on the Friday chat page (or just visit the dashboard and it'll be set automatically). Your chat history will load from Clid Storage instead of Firebase.

Service binding config (for self-hosters)

If you're deploying Friday + Clid Cloud on your own Cloudflare account, add the service binding to the Friday worker's wrangler.toml:

The Friday worker's validateClidToken and clidStorageGet/Set/Delete functions prefer env.CLOUD.fetch() when available, falling back to fetch() if the binding isn't set. Without the binding, you'll see Cloudflare error 1042 on every cross-worker call.

Friday Agent API Reference

The Friday Agent is an autonomous, tool-using AI agent — exactly like Z.ai GLM, Claude Code, or ChatGPT with tools. It plans, calls tools, observes results, then continues until your request is fully satisfied. Up to 8 reasoning turns per request, with a 14,000-character tool-result budget per turn. This section documents every endpoint, every tool, every auth method, and ships copy-paste-ready code samples in curl, JavaScript, and Python.

Contents

• Authentication — 4 key formats accepted
• POST / — non-streaming chat
• POST /stream/agent — SSE streaming
• POST / — mint a fri_agent_ key (type: agent_key_gen)
• POST / — list your agent keys (type: agent_key_list)
• POST / — revoke an agent key (type: agent_key_revoke)
• All 9 tools — full reference
• SSE event reference
• Clid Cloud — Vortex Fade integration
• Code samples (curl / JavaScript / Python)
• Error reference
• Rate limits + quotas

Authentication — 4 key formats

Every endpoint requires a fridayKey in the request body. The worker auto-detects the key format and routes through the correct validator. All four formats resolve to the same stable per-account uid, so a user's fri_agent_ keys are grouped together regardless of which auth method they used to mint them.

Recommendation: if you're building a backend integration, mint a fri_agent_ key (1-year expiry) and use it. If you're building a browser app on top of Clid, pass the user's clid_session from localStorage — the worker validates it transparently.

POST / — non-streaming chat

Sends a prompt to the Friday Agent. Returns the full agent trace after all turns complete. Up to 8 reasoning turns; ~30s timeout for the full loop. For long-running tasks (web search × 5, code execution), use the streaming endpoint instead.

Body fields:

• type — must be "agent"
• fridayKey — any of the 5 key formats
• prompt — the user's request (max 12,000 chars)
• history — optional array of prior {role, content} turns; the worker prepends these to the system context
• uid — optional; if omitted, the worker derives it from the key

POST /stream/agent — SSE streaming

Same body as the non-streaming endpoint, but returns a text/event-stream response. Tokens, tool calls, and tool results are emitted as they happen — ideal for live UIs. The stream stays open until the agent's last turn completes or an error occurs.

SSE event reference

Client-side tip: accumulate token events into a single text buffer per turn; when a message event arrives, that buffer is the final text for that turn. Render tool_call + tool_result as paired cards in your UI for transparency.

Mint a fri_agent_ key — type: agent_key_gen

Mints a new fri_agent_... key tied to the caller's identity. The key grants the same access as the parent key — it can call type:'agent', /stream/agent, and the chat-history routes. Expires in 1 year by default. The key is stored in KEY_REGISTRY KV (authoritative) and mirrored to Firestore or Clid Storage for portability.

Natural-language minting: you can also mint a key by asking the agent in chat — "please generate an api key for me" or "mint an api key labelled dev-laptop". The agent calls its generate_api_key tool and the new key appears in the chat reply.

List your agent keys — type: agent_key_list

Returns every non-expired agent key minted by the caller. Revoked keys are included with revoked: true for audit purposes. Each entry shows the masked key (first 14 chars), the full key (only if you stored it — the worker doesn't return the full key for already-minted keys), the label, mint time, and expiry.

Revoke an agent key — type: agent_key_revoke

Immediately revokes the specified fri_agent_ key. The KV entry is deleted, so subsequent requests using that key return 401 INVALID_KEY. Mirror entries in Firestore / Clid Storage are marked revoked (not deleted) for audit.

All 9 tools — full reference

The Friday Agent has access to 9 tools. The model picks which tool to call based on the prompt; you never invoke tools directly. Each tool's result is capped at 14,000 characters per turn to keep the agent's context window manageable.

Clid Cloud — Vortex Fade integration

The Friday Agent is also reachable through the Clid Cloud worker, which adds project-scoped access control, audit logging, and per-project key minting. These endpoints accept a Clid Cloud API key (clidkey_... or clid_live_...) or Clid session JWT. The target project must have the vortex-fade module enabled.

How it works under the hood: when you call the Cloud worker's /api/cloud/vortex/fade/agent endpoint, the Cloud worker:

1. Authenticates your Clid key via authenticate()
2. Looks up the project, verifies it belongs to your account and has the vortex-fade module enabled
3. Calls getProjectApiKey() which either fetches a cached clid_live_ key from KV (1-hour TTL) or mints a fresh one for the project
4. Uses the FRIDAY service binding to call POST https://friday.local/ with { type: 'agent', fridayKey: <project_key>, prompt, history }
5. Streams the SSE response back to the client transparently
6. Audits the invocation on the project's audit log

Code samples

curl — non-streaming

curl — streaming (SSE)

JavaScript — browser

JavaScript — Node.js (with fri_agent_ key minting)

Python — requests

Python — Clid Cloud Vortex Fade (project-scoped)

Error reference

Rate limits + quotas

• Per-key rate limit: 60 requests/minute, sliding window. Burst of 10 allowed.
• Per-key daily quota: 1,000 agent requests/day on the free tier. Friday Pro subscribers get 10,000/day. Admin emails are unlimited.
• Per-turn tool budget: 14,000 characters per tool result. Truncated results include a truncated: true flag.
• Max turns per request: 8. The agent stops early if it produces a final answer before then.
• Concurrent streams: 3 per key. Additional streams return 429 with Retry-After.
• Image gen: 50 images/day per key. Pollinations enforces its own rate limit on top.
• Video render: bounded by your json2video API key quota — currently ~595 seconds of video output remaining on the worker's key.

Try it

Sign in at cloud-6pp.pages.dev/dashboard.html#/vortex-fade, pick a project with the Vortex Fade module enabled, and chat with the agent. Type "please generate an api key for me" to mint a fri_agent_ key right from chat — then use it in any of the code samples above.

Daily Briefs & Notifications

Widget & install

Security

Installing Friday as an App

Friday is a full Progressive Web App — installable on Android, iOS, and desktop.

The service worker (sw.js) caches the app shell with a network-first strategy for HTML/JS (so updates land immediately) and a cache-first strategy for images/fonts. Push notifications are wired up; background sync ready for offline message drafts (rolling out).

Pricing

Privacy Policy

Last updated: May 2026.

What we collect. When you create an account: name, email, conversation history, and memory profile in Firebase Firestore. API usage logs (key, model, timestamp, prompt/reply length, grounding flag) in usage_logs. Bot conversations for bots you've published in bot_logs/{slug}/events.

Connector credentials. Tokens you supply for Slack, Notion, GitHub, HubSpot, Trello, Spotify, Shopify, Stripe, Google Workspace, Telegram, etc. are stored AES-GCM-encrypted at rest using a per-user key derived from a worker secret + your Firebase UID. The worker decrypts them only at the moment of executing an action you initiated.

Memory data. The memory system extracts facts and preferences from your conversations to personalise Friday. Stored under your account in Firestore; used only to improve your experience. You can clear it any time with the "clear my memory" command or request full deletion.

How we use it. Conversation history powers your own chat history and context injection. Usage logs power your Dashboard. Bot logs power your bot's analytics. We do not sell, share, or use your data for advertising.

Guest usage. Without signing in, nothing is persisted — everything is in-memory and cleared on refresh.

Third parties. Prompts are processed by Google (Gemini), Groq, and optionally Tavily. Images generated by Pollinations and uploaded to imgbb. Google Workspace actions hit Google APIs with your OAuth token. Please review their respective privacy policies. We send only prompt text + scoped tokens — no extra identifying information.

PII Detector. Friday's client-side intelligence layer warns you before sending content that contains common PII or secrets (emails, phone numbers, credit cards, NIN, BVN, API keys, private keys). You choose whether to proceed or redact.

Data deletion. Self-serve memory clear is available; full account deletion: contact admin@zylinkcorp.com.ng.

Terms of Service

Last updated: May 2026.

By using Friday F.ai, you agree to these terms. Friday F.ai is a product of Zylink Corp Group of Companies.

Acceptable use. You may use Friday for lawful purposes only. You must not: generate harmful, illegal, or misleading content; circumvent key validation or rate limits; scrape or harvest data at scale; reverse-engineer the gateway architecture; or use connectors to perform actions you do not have authority to perform in the connected accounts.

API keys. You are responsible for keeping your fri_ keys secure. Do not commit keys to public repositories. Zylink Corp reserves the right to revoke keys found in violation of these terms.

Connectors. You authorise Friday to act on the connected accounts you've linked. Connector credentials are stored encrypted; you are responsible for keeping the underlying tokens valid and revoking them at the provider when you no longer want Friday to act on your behalf.

Published bots. When you publish a bot via the Bot Builder, the rendered HTML is publicly served at /b/{slug}. You are responsible for the content of your bot — including its system prompt, knowledge base, and any third-party content you reference — and for ensuring it complies with applicable laws.

Service availability. Friday is provided "as-is". We do not guarantee uptime. The underlying AI models and third-party services (third-party AI providers) are outside our control.

Intellectual property. The Friday F.ai interface, branding, intelligence layer, and gateway architecture are property of Zylink Corp. AI-generated outputs are provided for your use — you are responsible for reviewing and using them appropriately.

Limitation of liability. Zylink Corp is not liable for any direct, indirect, or consequential damages arising from the use of Friday F.ai, including but not limited to decisions made based on AI outputs or actions taken by connectors on your authorised accounts.

Changelog

Contact