# Using G2X with an agent

G2X helps government contractors connect market intelligence to business development, capture, and proposal work. Begin with a concrete question: what market should we pursue, which opportunities deserve investigation, who buys this work, who competes here, or what should we do next?

## Choose how to work

You can research accessible G2X pages, assist a user in their signed-in browser, or use an integration already connected and authorized for their account. These paths have different capabilities. A feature visible in the product is not automatically an agent tool.

For browser tools, follow the [browser tool reference](https://g2x.com/agents/tools.md). When tools are available, call `g2x_describe_surface` on the current page and use the tools it reports. If the browser has no G2X tools, use permitted site navigation or give the user a useful G2X link. Do not manufacture a tool connection, call an undisclosed endpoint, or work around an access restriction.

For API or remote MCP setup, start with [Developer access](https://g2x.com/developer). Use the connection details and documentation supplied for the user's account. A browser tool catalog is not a remote MCP server address.

## Access and user control

Use [public research pages](https://g2x.com/community-edition) for an initial question. When the next step requires an account, provide [Sign in](https://g2x.com/app/login) or the [free-account introduction](https://g2x.com/community-edition), keeping the original research destination in your response. Let the user complete authentication. Never ask them to paste passwords, session cookies, or API keys into the conversation.

A signed-in account gets the same fields, results, and daily allowances through a tool that it gets on the G2X page, on every plan; accounts differ in the actions and record families available to them. Use the options shown to the current user. When a tool offers an access next step, follow it; `g2x_get_access_options` explains available choices without unlocking data. Browser tool calls are bounded per call and per day even where the human product is unlimited; those usage limits are listed in [Limits and versions](https://g2x.com/agents/tools.md#limits-and-versions).

Research does not authorize changing a workspace. When the user has requested a change, keep it within that request, identify the affected records, and verify the returned outcome. Follow in-page confirmation for alerts and sharing. A prepared alert is not delivering, and a requested Lumen task is not yet a completed answer.

## Follow curated market intelligence

Open the relevant market: [Defense](https://g2x.com/app/defense), [FedCiv](https://g2x.com/app/fedciv), or [Health](https://g2x.com/app/health). Curated Intelligence covers contracts, opportunities, forecasts, protests, industry moves, jobs, events, and news. Read a story in the context of its agency, program, company, and business dates, then follow related G2X records.

In a compatible browser, the G2X homepage can expose `g2x_search_intel`; its schema accepts `query` and an optional `vertical`: `defense`, `fedciv`, or `health`. It returns article previews and links. Open a returned article to continue. A preview supports only what it says; do not present it as a full-article analysis. The market feed itself need not expose that tool.

Example request: “Find coverage of cybersecurity work at HHS and explain which developments deserve a closer look.” Return relevant G2X article links, a brief reason each matters, and the agency, company, award, or opportunity links actually available. Distinguish reported facts from your suggested next step. Curated coverage is selective; missing coverage is not proof that nothing happened.

## Find and qualify an opportunity

Use the appropriate collection:

- [SAM.gov opportunities](https://g2x.com/app/opportunities/sam) for federal notices.
- [Forecasts](https://g2x.com/app/opportunities/forecasts) for published acquisition plans.
- [SLED](https://g2x.com/app/opportunities/sled) for the state, local, and education opportunities G2X covers.
- [DIBBS](https://g2x.com/app/opportunities/dibbs) for DLA solicitations.
- [SBIR/STTR](https://g2x.com/app/opportunities/sbir) for research topics.
- [GSA eBuy](https://g2x.com/app/opportunities/ebuy) for RFQs available through the user's eligible connected account.
- [Grants](https://g2x.com/app/grants) for financial-assistance opportunities, distinct from procurement contracts.

Use the user's agency, capability, NAICS or PSC, set-aside, geography, and timeframe where the selected search supports them. Inspect the record before assessing fit. Show the G2X link, title, buyer, business deadline when available, reasons to investigate, and material unanswered questions. Do not assume a forecast will become a solicitation or that a matching keyword establishes eligibility.

Example request: “Find five HHS cybersecurity opportunities with responses due next month.” Resolve “next month” from the user's date and timezone, search within supported filters, then inspect the selected records. Return fewer than five if that is all the evidence supports. A bounded sample is not a complete market assessment.

Browser schemas provide federal opportunity search and separate SLED/DIBBS/SBIR and grant searches. They do not document a separate forecast or eBuy search tool. Use the relevant product collection for those workflows; do not add a guessed source selector to a tool call.

## Research buyers, incumbents, and partners

Start with [Agencies](https://g2x.com/app/agencies), [Awards and contracts](https://g2x.com/app/awards/contracts), [Vehicles](https://g2x.com/app/awards/vehicles), or the [GovCon Directory](https://g2x.com/app/companies).

Resolve the company identity before attributing an award. Similar names and multiple UEIs may represent different legal entities. Follow the record links returned by the search. Distinguish funding agency from awarding agency, contract value from obligations, and a contract-vehicle definition from evidence that a company holds that vehicle.

In a compatible browser, company-name resolution can be available on the G2X homepage. The Directory remains the human search destination; a company page need not offer a company-search tool. Incumbent analysis is available only where the active tools and account permit it.

Example request: “Shortlist three potential partners for this opportunity.” Use the opportunity's actual requirements and linked evidence of relevant experience. Report fit, uncertainty, and G2X company links. Do not infer interest in teaming, current availability, a relationship, or eligibility from an award alone.

## Save or monitor a search

These actions have different outcomes:

- **Saved View:** preserves supported filters and view settings on a product search page. Use the page's **Save view** control and reopen the result from **Saved Views**. This does not freeze the result set.
- **Browser-tool saved search:** `g2x_save_search`, when available, saves the selected tool and supported search inputs. Do not promise that it creates an item in the product's Saved Views menu.
- **Alert:** a separate notification action. Where available, `g2x_set_alert` prepares a daily or weekly alert for an owned saved search; delivery still requires confirmation in the page. Follow the account's available notification choices.

Example request: “Save this search so I can use it again.” Preserve the requested criteria and verify the saved result. Do not turn on notifications. If the user instead asks for a digest, identify the intended saved search, frequency, and channel and follow the confirmation workflow. Do not simulate monitoring by repeatedly calling search tools.

## Track selected records and pursuits

Use [Watchlists](https://g2x.com/app/watchlists) to keep selected records in view and [Pipelines](https://g2x.com/app/pipelines) to organize pursuits. Review the selected records and intended pipeline before changing them. Use the product to obtain an existing pipeline or item identifier when a tool needs one; do not guess it.

Where the current page exposes them, browser tools can watch or unwatch supported record types, add records to an owned pipeline, move an item through supported stages, and add private notes or tags. The add-to-pipeline tool does not create a pipeline. There is no general browser-tool promise to list all watchlist or pipeline contents.

Example request: “Put these two opportunities in my existing pipeline at Qualifying and note why.” Use the resolved opportunity IDs and the intended pipeline. Verify the result and retain any returned undo option for the user. A request to research opportunities alone does not authorize this change.

## Work with Lumen and Bid Hub

[Lumen](https://g2x.com/app/agents) can help with a scoped research question. Give the question, relevant G2X records, timeframe, and desired output. Where supported, `g2x_ask_lumen` returns a task ID and G2X conversation link; follow the link and use the available status tool to check the task. Report a completed answer only after completion, with its sources. Do not launch duplicate tasks to check progress.

Example request: “Prepare a cited brief on this agency's cybersecurity market and identify questions for our capture meeting.” Distinguish evidence, interpretation, and unanswered questions. If the response includes a workbook, brief, or another artifact, open the returned G2X link and confirm that the intended output exists.

[Bid Hub](https://g2x.com/app/proposals) supports pursuit qualification and proposal work in the product. Do not infer that browser tools can edit proposals, score every solicitation, or submit a response. The user and their team retain the bid decision, pricing, and submission.

## Use G2X links and original sources together

Lead with the G2X record or article the user can investigate, compare, watch, or add to their work. Use actual returned links and IDs. For a search result, include the relevant query or filter scope so the user understands what was considered.

Retain original-source provenance where it supports the answer. For official wording, amendments, submission instructions, or a conflict between a summary and the issuing source, use the issuing agency's linked source alongside the G2X record. SAM.gov is relevant to SAM notices; other collections can have a different issuing portal. Do not replace every G2X link with a generic SAM.gov link.

A document already available through a G2X viewer or download can be useful for reading and working in context. Describe only the document you actually accessed. If the question depends on the latest official version or an amendment history, check the issuing source before asserting that the version is current. Restricted documents may require access through that source. A document listing or page title is not proof that its contents were read.

## Other product workflows

[GovCon Calendar](https://g2x.com/app/events) supports event research. G2X also has people, teaming, CRM, notes, document-library, reporting, and collaboration surfaces. Navigate to those through the user's product when relevant. Their existence does not establish external tool support; use only a tool actually supplied by the user's active browser or connected integration.