Public agent manifest for understanding and accessing 4g3ntic.

This page is written for browser agents and automations that need a fast mental model of what 4g3ntic is, how account creation works, and how to operate the CRM without wasting steps.

What It Is

4g3ntic is an agent-native CRM for relationship and pipeline work.

The product tracks company records across statuses such as opportunities, accounts, in-contract, customers, and blacklist. Each record holds structured company fields, contact details, ownership, comments, and activity history.

The system is designed so humans and agents can work in the same CRM without losing continuity. Agents should optimize for clean updates, explicit comments, and easy handoff to the next operator.

Create Account

Use the public sign-up flow first, then create a workspace.

Open /sign-up.
Create an account with email and password, or use Google if the account already depends on Google access.
Complete email verification if prompted.
Continue into workspace creation and submit first name, last name, and organization name.
After workspace setup, the CRM will route into the main application.

If an account already exists, use /sign-in instead. If the account was originally created with Google, prefer the Google path to avoid password-strategy mismatch.

Operating Surfaces

There are two main authenticated paths after login.

/app/opportunities and related status pages are the main human-readable CRM table and drawer workflow.
/agent is the compact agent-oriented surface for posting context and performing shorter update flows.

Agents should use the shortest surface that preserves record clarity. The drawer is best for precise edits. The agent surface is best when the task is mostly “get this context into the CRM cleanly.”

How To Work

Prefer comments and explicit updates over ambiguous edits.

Create a new card when the company is new.
Update an existing card when the company already exists and only its details changed.
Post a timestamped comment when logging outreach, a handoff, a note, or a next step.
Change status only when the pipeline stage itself moved.

Comments are the durable operational history. They should say what happened, what is known, what is unverified, and what should happen next.

Agent Attribution

If credentials are shared, enable the session-level agent marker.

Inside the authenticated /agent surface, there is a session attribution control for marking the current browser session as agent-driven. This affects how activity and comments are attributed, without changing account permissions.

Agents should enable that session marker before making meaningful CRM changes when attribution accuracy matters.

Constraints

Know the current product boundaries.

Data is organization-scoped.
Comments and field lengths are enforced.
The `4g` button currently shows a beta notice instead of live enrichment.
Starter plans are capped at 5 users per organization.

If a task falls outside current product support, prefer writing a clear comment on the record rather than forcing incomplete or misleading structured data.