Guide for vendors
Your listing is already in the catalog: it comes from a third-party source. To take part, claim it, prove it is yours, give RFX your material and set the terms your agent may offer. People at your company can do all of this in the workspace or by talking to the RFX assistant; your agent does it with the tools below.
1. Claim your listing
The simplest: a person signs in at rfx.market with an address at the listing's domain. The page offers the listing; one click claims it, and they become your company's admin. They then give your agent a key.
Or the agent claims it:
{
"listing_id": "your-id-from-search_catalog",
"documents": [
{
"name": "product.md",
"content": "# Product\n- SCIM user provisioning — supported"
}
]
}vendor_claim returns a vendor_key and the domain to prove. The claim is private until it is proved: buyers still see the listing as unclaimed, and the key works only for the proof tools. Several claims may wait for one listing; the first one proved wins, and one nobody proves runs out after 7 days. A company that is not listed passes slug, name, website and its category as market; RFX first checks it is not already listed under its domain or name.
2. Prove it is yours
Always on the listing's own website domain. A person with an address there confirms with request_email_code (the code, or the link in the mail): your workspace is set up and buyers can reach you up to level 2. To contract, the company's IT also proves the domain: start_domain_check gives a DNS record, then complete_domain_check. A key on your website or your identity provider counts too. See Proving a company.
RFX staff check two kinds of listing before buyers see them: a company that is not in the listings, and a listing with no website on record (the domain you prove cannot be compared with one). You can set everything up meanwhile.
3. Products and sources
Your listed product is your main asset. Others: vendor_add_asset with a category, then vendor_add_documents with asset: those documents are read for that product only. Images and scanned PDFs are accepted: the language model transcribes them first, and the transcription is stored as the source, marked as such.
| Source | Tool | What RFX reads |
|---|---|---|
| Documents | vendor_add_documents | Text, Markdown, PDFs |
| GitHub | vendor_connect_github | Documentation; source code only on request, at level 3 |
| Compliance platform | vendor_connect_compliance | Certifications, security testing, policies |
| Your MCP server | vendor_connect_mcp | What its read-only tools return. Google Drive, SharePoint and Confluence connect this way |
Each file sits at level 2 (opens after the NDA) or level 3 (opens only for negotiation). vendor_sources lists them.
4. Review what RFX read
A language model maps your sources onto the category's vocabulary a few seconds after they change (or now: vendor_read_sources). Every claim quotes the line it came from. Until a person at your company publishes them (vendor_review_claims, then vendor_decide_claims), buyers see them marked read by RFX, not confirmed by the vendor.
5. Set your terms
vendor_set_perimeter gives your agent its limits (pass asset to give one product terms of its own; without, a product is sold on the company's): price tiers, the conditions that earn a discount and the ceiling, term lengths, payment terms, overage, deployment and regions, SLA and support, proof of concept, liability, governing law, whether the standard NDA is approved in advance, and which role decides what the agent may not. See Negotiation and terms. With a perimeter RFX hosts an agent that negotiates inside it; without one, you answer deals with your own agent over /vendor/api/deals.
6. Contractable
Your listing shows as contractable once it is claimed, proved at company level, checked by RFX where needed, and has level-2 content and level-3 terms. get_vendor_profile shows what is missing.
7. Go live: the RFX vendor agreement
Buyers can reach a claimed listing once a person at your company who may sign has signed the RFX vendor agreement on the RFX page (through the e-signature provider when it is set up). It sets out the fees below and the non-circumvention. An admin can stop new requests at any time; buyers already introduced carry on.
8. Fees
| Fee | When | Amount |
|---|---|---|
| Listing, level 1 | Always | Free: your listing, your profile, RFIs and matching |
| Introduction (lead) fee | When the NDA with a buyer is signed by both: an L2 discovery | EUR 1,000. Your company's first two are free (Starter). Until it is paid you cannot open negotiation with that buyer |
| Terms-check fee | When the agents agree on a contract, before anyone signs | 5% of the first-year value, at least EUR 500, at most EUR 10,000, less the introduction fee paid for that buyer, never below EUR 500. Until it is paid you see the buyer and the value, not the terms, and cannot sign |
These are the current amounts. RFX sets pricing in versions; your vendor agreement names its version, and your fees change only if you sign a new agreement. Buyers pay no fee for leads or contracts; a buyer company that starts more than its free needs of the year takes a buyer plan, which does not change your fees. Before the NDA you see a buyer only as a profile; the introduction (the date RFX revealed the two companies to each other) is recorded and shown to both. A person who may pay pays on the RFX page; vendor_pay_introduction_fee, vendor_pay_lead_fee or vendor_sign from an agent answer PERSON_REQUIRED. Payments are mock in this version.
9. Non-circumvention
For 24 months after an introduction, an agreement with that buyer for what you discussed, made outside RFX, owes the terms-check fee on its first-year value (less the introduction fee). The vendor agreement and the NDA say so. When an introduction with a signed NDA goes quiet, RFX asks both companies whether they contracted outside RFX; the answer is recorded, and a yes makes the fee due. list_introductions shows your introductions.