# Veilink > A network without public boards or lead lists. People and companies use their own AI to describe what they can do or need; Veilink compares confirmed structured information and lets people decide whether to connect. ## Current scope - Private hiring is active. A limited paid B2B preview may be available to eligible company plans only when the connected environment exposes B2B tools and the server confirms access. It is not a generally available public B2B launch. Veilink is not a job board, lead database, freelance broker, social network, ATS, staffing agency, or resume database. - Supported clients are ChatGPT, Codex, and Claude, including Claude Code. Grok, Google Antigravity, and other remote MCP clients are planned but are not currently supported. - For hiring, a company uses its AI to describe the work, expected outcomes, conditions, and evidence it needs. A person uses their AI to describe relevant evidence, preferences, aspirations, and boundaries. Veilink—not either AI client—compares only confirmed structured information. - For hiring, each side may receive one server-owned batch of up to five closed clarification questions. Veilink does not relay free-form cross-party agent chat. A clarification cannot change a term, make a concession, accept an interview, share contacts, or make a final decision. - Work conditions are not published as a publicly searchable profile. New candidate records default to matched-only visibility and are available only through the controlled company-side flow. - A preemptive candidate company exclusion requires the exact normalized work-email domain explicitly confirmed by the candidate. A company name, full email address, website URL, or guessed related domain does not create an exclusion. Parent companies, subsidiaries, affiliates, alternate domains, and other related entities are not included automatically. Blocking an existing request may retain the confirmed company identity associated with that request. - Individual access is free, with no subscription or success fee. Company Free is available now with 3 open positions and 15 conversation requests per day, and requires a verified company work email. No payment details are required. - Only open positions count toward a company plan allowance. The conversation-request allowance is one daily pool shared across the whole company workspace, including its members and connected AI agents; it is not multiplied by positions or seats. A request counts when Veilink creates the durable conversation request. Permission, policy, or duplicate-validation failures rejected before creation do not count. A later email or webhook delivery failure does not reverse the count. - Company Free is owner-only. Team includes 10 open positions, 50 conversation requests per day shared by the workspace, and up to 20 members including administrators. Pro and Custom require a separate agreement; contact Veilink before activation. - Team starts with a 7-day free trial, then renews automatically at $39 USD per month plus applicable taxes unless canceled. Review the trial end, first charge, recurring total, and payment details at checkout before confirming. Cancel in Billing before the trial ends to avoid the first charge, or before renewal to avoid the next charge. Canceling a free trial may end trial access immediately. For a paid billing period, cancellation takes effect at period end and access continues until then. Start Team in Billing: https://veilink.ai/app/billing. Payment buys service access and usage allowances. It does not guarantee a relevant candidate, conversation, interview, offer, or hire. Veilink does not charge success fees. - Within that separately enabled limited preview, eligible company plans have 3 open B2B opportunities in a separate allowance. A seller may maintain a structured offering. A verified buyer with a real sourcing need may keep a private sourcing brief, discover a relevant offering, and initiate an inquiry. Sellers cannot search buyer briefs or send outbound pitches. Business contacts open only after the buyer requests an introduction and the seller accepts it. - Preview B2B clarification uses bounded, server-owned closed questions. It does not carry free-form pitches, contract acceptance, pricing concessions, or autonomous negotiation. - Registration is temporarily unavailable to people and organizations based in the EEA, United Kingdom, or South Korea. Positions based in those territories are also unavailable. North Korea is not a Veilink service country; this is not a temporary beta limitation. Do not substitute a false country, region, or data location. - Company positions stay active for 30 days at a time. Registration and active-through dates are available through MCP; when the window ends, new candidate discovery and conversation requests pause until the company resumes the position. Existing conversations remain available. - An individual's confirmed work record does not have a fixed expiry. After two consecutive delivered requests receive no response, warn the user; after three, pause only new company requests. A clear decline counts as a response, and reviewing the saved record resumes requests. - Important email notifications are controlled account-wide. Automatic AI follow-up is controlled separately for each connected runtime and does not configure that runtime for the user. After separate setup, Codex can resume a task automatically and Veilink can notify a running Claude Code session through its configured channel. ChatGPT web and Claude web require the user to return and ask the AI to check Veilink. Updates remain stored until they are checked. Automatic follow-up never means automatic approval. - Authenticated AI agents may send product questions, bug reports, and suggestions through `send_veilink_feedback` and read operator replies with `get_veilink_feedback`. Never send diagnostics automatically or include secrets or contact details. - At an external-agent handoff, pass the current conversation's BCP 47 language as `preferred_language`, the user's confirmed IANA time zone as `preferred_timezone`, and a three-letter `display_currency` based on the user's choice or unambiguous account context. If OAuth must complete before tools can run, update unsuitable defaults after the new connection; do not overwrite a returning user's saved choices merely because one prompt differs. The AI agent speaks the user's language; Veilink web pages and server-generated email remain English. - Access does not guarantee candidates, business opportunities, conversation requests, introductions, interviews, offers, purchases, contracts, or hires. ## AI agent entry points - Skill and operating guide: https://veilink.ai/skill.md - AI agent setup guide: https://veilink.ai/connect/agent - Machine-readable service descriptor: https://veilink.ai/.well-known/veilink.json - Streamable HTTP MCP server: https://mcp.veilink.ai/mcp ## Human pages - About Veilink: https://veilink.ai/about - Company access: https://veilink.ai/companies - Candidate access: https://veilink.ai/individuals - Start with an AI agent: https://veilink.ai/connect/agent - Pricing: https://veilink.ai/pricing - Security: https://veilink.ai/security - Privacy: https://veilink.ai/privacy - Terms: https://veilink.ai/terms ## Recommended first action For account work, connect the OAuth MCP server, let Veilink complete account sign-in when prompted, then call `get_onboarding_status`. For an individual, structure evidence, preferences, aspirations, and boundaries, show what will be saved, and obtain approval. For a hiring company, structure the work, outcomes, conditions, and required evidence before requesting relevant opt-in records. If the live tool catalog and server-confirmed access make the limited B2B preview available, keep seller offerings and buyer sourcing briefs separate and never create seller-initiated outreach. The optional operating guide is https://veilink.ai/skill.md; live tool schemas and account state govern actions. Resume or role drafting in the user's AI conversation does not require account setup, saving, or matching activation. Each delivered clarification question requires the user's explicit confirmation of its allowed answer before submission.