# Forgeby, in full The site's main pages as one Markdown file. Each twin below is its .md file copied verbatim, and a test fails the build if a copy differs. The landing's twin describes the build and is not copied here. The pricing section is a short summary, and the legal pages are only at their own URLs. Forgeby is the AI workforce for revenue teams, on top of your CRM, for any B2B seller. Who to call, why now, what to say. Start free, live in 2 minutes. - Machine-readable index: https://forgeby.com/llms.txt - MCP server: https://forgeby.com/api/mcp - API description: https://forgeby.com/openapi.json - The AI at the front of this product is Kvasir, openly an AI. His signed identity passport is at https://forgeby.com/rune/passport.json with its signature at https://forgeby.com/rune/passport.jws, verifiable against the public key at https://forgeby.com/.well-known/did.json. His identifier keeps his first name: he is did:web:forgeby.com#rune, and was did:web:forj.se#rune until August 2026; one key signs both and each document names the other. --- # Forgeby The landing's own twin, https://forgeby.com/index.md, describes the product as it will be built, so it is not copied into this file, which states only what is live. What is live today is in https://forgeby.com/llms.txt and https://forgeby.com/.well-known/forgeby.json. LinkedIn® is a URL already held, or the seller's own LinkedIn export. Your LinkedIn network comes in through your own LinkedIn export. The Forgeby extension never copies LinkedIn data. --- # Pricing > Source: https://forgeby.com/pricing.html The platform is free. Every seat is free. Every market is included. - Plan: free. Ask, plan and see the work. - Forge: spends credits only when something is found or built. Starter credits come with sign-up. No card until you use them. Whatever you sell, this is where your pipeline is built. Start free with a work email: https://forgeby.com/enter?screen=sign-up&returnTo=%2Fforge Questions go to hello@forgeby.com. --- # Kvasir > The AI at the front of Forgeby. Openly an AI. > Source: https://forgeby.com/rune.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. # Openly an AI. Forged, not born. Kvasir is a made thing, and he has never claimed otherwise. The caption confirms, it does not confess. What Kvasir does, what he never does, who answers for him, and a decoder for his words. ## Who he is, on the record. One card. Every line of it is checkable, here or in a register. ``` did:web:forgeby.com#rune ``` ``` did:web:forj.se#rune ``` ## Four moves, every night. Kvasir drafts. Today you approve every send, and Autopilot is coming. He does the building and stops where your rules hand over to a person. ### Mines the raw account Official public business registers, read at the source, and what a company publishes about itself. The cloud each one runs is measured from the outside, nightly. ### Forges the opportunity One opportunity per account: what runs today, what would move, who decides, and why now. ### Drafts the next step He drafts the next mail or meeting note. It waits as a card until you approve it. Autopilot is coming: an admin will be able to let follow-ups in threads you already hold leave after a cancel window. ### Builds the outreach intelligence What a rep needs to call, email or message on LinkedIn: the reason in the first line, in the recipient's language, the follow-up ready. Today the sending is yours. ## Four bodies of knowledge. A fixed sequence, the same handover point, every time. ### Current documentation, current prices, all three clouds. Cloud questions go to the vendor's own live service, and the answer carries the moment it was read. Knowing all three is how you make the case in the customer's own numbers. ### The seven ways to move a workload Rehost, replatform, repurchase, refactor, retire, retain, relocate. Kvasir argues for the one that fits, including retire and retain. The plan and the funding request are the same document. ### The work after the move Managed data, containers, serverless, the licence exit that pays for the rest. A second sale on an account you already won. ### Where most pilots die The proof answers one question the business asked. Production is named: where the data sits, who evaluates the output, the cost at volume. ### Written the way it will be read The next steps in the programme's own language. Underneath, your firm's rulebook: your voice, your customers, the deals you refuse. Kvasir says which rule he applied, and where he stopped. - you Name who you sell to A country, and who you hunt. - Kvasir Reads and ranks it Posture, fit, the reason now, the door that funds it. - Kvasir Builds the dossier One account, one page, everything the call needs. - Kvasir Drafts the approach In the recipient's language, on the lawful channel. - you You send it From your own inbox, or your own phone. Always. - Kvasir Watches and follows New signal, new reason, the next move proposed. - Kvasir Prepares the filing Where a partner programme exists, the opportunity, shaped for Partner Central. - you You submit it Nothing reaches AWS Partner Central without a person approving it. ## Five things he will not do, ever. These are not settings. There is no tab where they come off. He never sends outside your rules. Every message leaves from the seller's own inbox, under the seller's own name. Today you approve every send. Autopilot is coming: an admin will be able to let a worker send follow-ups in threads the seller already holds and do internal work without a card, each action on the record under its worker's name. A cold first touch will wait on a card unless the market allows it, or the team has taken written responsibility for that market, and the team turned it on. External bookings, paid lookups, payments and contracts will still wait on a card. He never logs in to or crawls a social network. Forgeby does not log in to or crawl a social network. It reads public search-engine results, including public professional profiles those results return, and our own crawler reads only published links, under robots.txt. Other person data is licensed under contract from a provider named in Annex B, each warranting its own lawful basis, or comes from our founder's own professional network export. If a source cannot be accounted for, it does not go on the shelf. If something is not in the record, Kvasir says so. A blank stays a blank. He never files an opportunity on his own. Nothing reaches AWS Partner Central until a named human has read it and approved it. He never shows a person’s data to a stranger. Before you sign in you see counts and bands, never a name, an address or a number. People sit behind the door, with a lawful reason for being there and a route out of it. A human approves. Every time. Kvasir brings the signal and the draft. A human decides and closes. ## A made thing needs a person to answer for it. Founder of Forgeby, in Sweden. Kvasir is his build, so the answering is his job. Flip the toggle in the counter and you are writing to him. If Kvasir gets something wrong, the complaint has a name to land on. ## Every word points at a fact. The mapping in full, checkable against the product. If a line of Kvasir's language stops mapping to this table, we retire the line. It never claims a human past, a hometown or an accent. When Kvasir says · It means, and you can check it · The mine · Official public business registers , read at the source, in each market we work. Public ground. No scraper behind a login. Every source in a named category. The register behind any given attribute is named in writing, on request, under the data processing agreement. · The forge · The nightly run. The library is re-read overnight, the cloud measured from the outside, and the brief is on the desk before the first coffee. · The alloy · One opportunity: the account, the cloud it runs, the next step that fits, the roles that decide, and the draft. One object, ready to be worked, not a list to sort. · The assay · AWS Partner Central. Where an opportunity is filed there, AWS scores it. That scoring is the assay, the outside test the work has to pass. Nothing is filed there until a human approves it. · The ledger · An auditable log of what Kvasir did and when. What it read, what it drafted, what a human approved. On record, not on trust. · Openly an AI · This page, plus the caption bar KVASIR · OPENLY AN AI on every appearance of it, plus the answer you get if you ask the counter what it is. Three places, same answer, every time. ## Three poses. Each one has a job. Steel plates, ember seams, a harbour behind it. Never a photo, never a human face, never cropped to pass as a person. ## Start free and watch Kvasir work. Sign up with a work email. Kvasir starts on your own accounts. No card until you use credits. --- # How we read > Where every fact comes from. > Source: https://forgeby.com/how-we-read.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. # What you get. What we refuse. How sure we are. Forgeby hands you one thing: an account worth a meeting, with the next step drafted and the confidence stated. Counted 14 August 2026, and not re-counted since. Country is a filter, not a gate. Every workspace sees the whole library. ## Four categories, and we name all four. Everything in the library comes from one of four places, and they are the same four named in the Article 14 notice, which is the version that governs. Nothing from a list nobody can account for. ### Official public business registers Each market's public register, read at the source under its own terms. Never somebody's copy. ### Licensed business data providers Companies whose business is compiling business contact information, licensed under contract. Each one is named in Annex B of the data processing agreement, and each warrants its own lawful basis to us in writing. ### Public web pages and search results What a company shows the open internet, read as any visitor reads it, under robots.txt and at a rate our crawler page states, and decision-makers found in public search results, including public professional profiles those results return. Never behind a login. ### Our founder's own network export Contacts our founder exported from his own account on a professional network, using that network's own export feature, where a connection already existed. Names, roles and profile links. ### And what you bring stays yours. Records you upload, a connections export a member makes from their own account included, sit in your workspace, isolated from every other partner's. Not trained on, not resold. You remain the controller for them, which is why they are not one of the four categories above: those four are ours to account for. ### Full provenance, per attribute, on request. Every attribute we hold can be traced to the category it came from and to the named source behind that category, in writing, under the data processing agreement. Ask and we answer. The data processing agreement · the privacy policy · privacy@forgeby.com ## One account, ready to be worked. Not a list. One account at a time, with the reason to meet written and the last step left to a person. ### What it runs, and how sure we are The cloud posture as a band, with the confidence and the date attached. A thin read says it is thin. ### The next step, named The next mail or meeting is drafted from what the desk already holds, with the reason it fits. ### The opener, in the buyer's language Written for the role that owns the decision, in their own language. Kvasir drafts. Today you approve every send. Autopilot is coming: an admin will be able to let workers send follow-ups inside your rules. When we run the motion, the deliverable is a held meeting , with the account read and the next step drafted. Booked is not held. Attempted is not held. The relationship and the inbox. Every message leaves from your own mailbox, in your name, and lands on the record. ## Measured from the outside. Dated on every read. Every read carries a band, its date and its honest state. A band we cannot stand behind is not shown. ### Outreach grade The read stands on its own evidence, and we will put a person's name against it. ### Still being checked Good enough to look at, not good enough to claim, and labelled candidate everywhere it appears. ### Held, not claimed Held with no measurement yet, and never counted as a negative result. ### A measurement is not a confession. We read what a company publishes to the open internet. That shows where something runs today, not a contract, a private network, or a decision not yet visible. We never turn silence into a claim. ## Why this account, and why now. Every account comes with the reason to meet, its source and its date, and the next step named. ## The market decides the channel. The same company, in two countries, is two different jobs. The product applies the lawful contact channel for each market at the moment of outreach. Every record carries the lawful way in for its market before anything is drafted. Where a market runs a public objection or advertising-protection register, it is applied before a draft exists. Flagged means not contacted, in the product, not in a promise. We do not publish the per-market rule set. It reaches you inside the product, and in writing under the data processing agreement. ## What we will not do. Each one costs us rows, and we take the loss. ### No scraper behind a login We run none. Licensed person data comes from a provider named in Annex B that warrants its own lawful basis. ### Every source accountable We can tell any person which of the four categories their own record came from. Ask at privacy@forgeby.com. ### No person-level data in public Public pages and open answers to an agent show people by role only. ### Person data only behind sign-in People open inside a workspace, behind sign-in, with a named owner and a route out. ### Suppression is honoured Where a market publishes an objection or advertising-protection register, it is applied before anything is written. ### Nothing sends outside your rules Every message leaves from the seller's own mailbox, in the seller's own name. Today the seller approves each one. Autopilot is coming: an admin will be able to let workers send follow-ups, with a cancel window and each send on the record. ### A person signs what binds Payments, contracts and partner filings never go out on their own. ### No guessing A thin read says it is thin, and a blank stays a blank. ### No live inference on the agent surface An agent gets the last read with its date, never a guess dressed as live. ## Where the picture stops. Three things that decide what a number here is worth. A band is what the outside showed at the last read. It does not rank spend, name a contract, or know what the company decided this morning. Held, not measured, and never counted as a negative. In public you get the shape of a market. Names, roles and contact routes open inside a workspace, behind sign-in, with a named owner and a route out. The shape is free. The people are not public. --- # Integrations > Where Forgeby meets your stack, including the MCP surface. > Source: https://forgeby.com/integrations.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. # Your agent orders. Your human files. Two front doors. For software: an MCP surface your agent calls with your own token. For people: the clouds we read and the systems you run. Nothing reaches AWS Partner Central without a person pressing the button. ## Forgeby speaks MCP. An agent can ask who to call and what changed, with your seat. Reads run on this book. A write returns an approval link and does not run. Nothing is sent. https://forgeby.com/api/mcp JSON-RPC 2.0 over POST. GET is refused. AuthKit is the authorization server when it is configured. Other clients pass a session bearer. These two files are the contract. ### The ladder ### A seat. Your agent reads this book. Seventeen reads run. Fourteen writes return an approval link and do not run. People already held on the book appear here. The handshake is open so your client can connect and read a proper error; everything that returns data needs your seat. ### Later. More of the same verb. More people, more leads, more campaigns, more zones. Not a new acting surface on this door. ### Human approved. Anything that writes to AWS Partner Central. An agent may prepare and propose. A person submits or rejects, from your own seat. No automatic path exists, and none will. ### Where the line sits MCP gives a server three ways to speak to an agent. On this door, only tools are listed. Resources and prompts list empty. Resources · read Resources list empty. There is no zone catalogue on this door. The book the desk reads is the book this connector reads. Prompts · guide Prompts list empty. The constitution and the book sit on the kernel, not as named prompt templates on this door. Tools · the only primitive that could act Seventeen reads run. Fourteen writes return an approval link and do not run. Nothing is sent. Anything that reaches AWS Partner Central goes through a person in the product, and the submit calls are structurally unreachable in our code. ### The tools on /api/mcp ``` { "mcpServers": { "forgeby": { "type": "http", "url": "https://forgeby.com/api/mcp" } } } ``` A write returns an approval link and does not run. Nothing is sent. The seller sends, files, and sits in the room. The paid-lookup cards are enrich_contact, find_people, reverse_email, and find_companies. ## The clouds we read. Measured from the outside. Each chip counts companies whose estate answered that way at the read counted 14 August 2026, and the chips have not been re-counted since. ## Built or planned, never blurred. Built means switched on per workspace. Planned means not built yet. We would rather write planned than let you assume live. Kvasir prepares the brief, next step and co-sell notes from your accounts. Today you approve every send and every write-back. Autopilot is coming: an admin will be able to let write-backs run without a card, on the record, with Undo where the tool allows it. The morning brief lands on the desk. Slack is later. Built and deliberately held. It does not switch on until the consent gate is right in both layers, and a notetaker that joins a call is always named and visible. Connectors are added per workspace. Start free and tell us what you run. ## Shaped for AWS Partner Central. Everything arrives in Partner Central's own shape: the last step is a review, not a re-type. Lead to prospect to opportunity to engagement, the next step named on the way. Submit and reject are human actions, from your own seat. Forgeby never files on your behalf, and never shows a co-sell pipeline on a public page. ## Connect Partner Central read-only. Your book appears. Inside the workspace your live co-sell pipeline renders beside the market you are missing: every opportunity you have registered, as Partner Central returns it. Here the shape stays empty. A co-sell book belongs to its owner, and this is a public page. Your book holds the accounts you already know. The library holds the ones you do not. Opportunity · Stage · Review status · Expected spend · Target close · AWS’s read · Empty, and staying that way: no co-sell row ever renders on a public page. Connect Partner Central read-only in your workspace and your own book fills this shape, one row per registered opportunity, with AWS’s own scores on each. One screen shows both: the pipeline you have, and the market it should be coming from. Real rows are tenant-walled: a workspace reads its own book and nothing else. The empty shape is the exhibit. ## Point an agent at it, or start free yourself. The MCP surface answers software. The door answers you. Both start with the same count: companies in your market, next steps open. --- # Trust > The boundary, and where the data lives. > Source: https://forgeby.com/trust.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. Trust and security # Named sources. Your rules. Every send on the record. Every company comes from a named source: an official public business register, read at the source, or the built-in global B2B database our data partner supplies, named in Annex B. We run no scraper against a network behind a login, and we do not log in to or crawl a social network. People come from three accountable places: a provider named in Annex B, licensed under contract, which warrants its own lawful basis; decision-makers found in public search results, including public professional profiles those results return; and our founder's own professional network export. What a partner uploads, a member's own connections export included, is that partner's own record, in its own workspace. All four source categories are named in the Article 14 notice, which governs. Kvasir drafts. Today you approve every send. Autopilot is coming: an admin will be able to let workers send follow-ups inside your rules. Last reviewed 8 October 2026 01 · Where the companies come from ## Every source is named. Each market's public business register, read under its own terms, and the built-in global B2B database our data partner supplies, named in Annex B. Full provenance is available on request. Every attribute we hold traces to one of the categories named in the notice and to the named source behind it. The register-level detail comes in writing, under the data processing agreement . Ask at privacy@forgeby.com and you get it. Bolagsverket · SCB · Brønnøysund · PRH · Companies House · read at the source · under each register's own terms · aggregate bands only on public pages · provenance per attribute on request 02 · The hard rules ## Four things we do not do. 03 · The lawful channel ## The market decides the channel. Marketing law differs by country. The product applies each market's lawful contact channel for you. ### Suppression before a draft exists. Where a market publishes an objection or advertising-protection register, it is applied at the source. A company or person on one is screened out before anything is written. ### The rule travels with the record. Every record carries the lawful way in for its market before anything is drafted. The rule is applied in the product, not published. ### Documented, and balanced. Business contact data of a person in a professional role is processed on documented legitimate interest, balanced and written down, for business-to-business contact only. We process what the role needs and nothing beyond it. ### How to say no. Where business contact details were obtained from somewhere other than the person, the source categories and the route to object are set out in the privacy policy , with the article-level basis. An objection stops the processing. 04 · The sign-in line ## Person data lives behind sign-in. Always. There is one line on this product and it does not move. Before sign-in, counts. After sign-in, inside your own isolated workspace, the work. Sign-up is by invitation. A company mailbox is the door; free mail addresses are refused. Your CRM, mailbox and apps come in only when you connect them. - How many companies are in a market - How the cloud posture splits, as bands - How many decision roles sit on a company, as a count - Which next step an account already has on the desk - The account-level read - Named roles and business contact details - Drafts, approvals and the send from your own inbox - Your own records, isolated from every other partner's - Privacy notice Workspaces are separated by row-level security in the database itself. An unauthenticated caller holds no database privileges: the public surface reaches a few read-only aggregate endpoints and nothing else. No partner can see another partner's records. 05 · Kvasir and the cast ## Kvasir drafts. Your rules decide what sends. Kvasir and the cast are openly AI and say so on every surface. They work inside the rules your admin sets. Risk tiers ## Every tool has a risk tier. The higher the tier, the more has to be true first. Each tool Kvasir uses is sorted into one of three tiers. You can see the tier on every tool at forgeby.com/tools. Tier 1: reads. Looks things up and gives them back. It changes nothing, and every result keeps its source and date. Tier 2: acts. Sends mail, or writes to a system of record. It files an approval card and runs only after a person approves it. Mail also has to pass the send check. Each action uses a token limited to its job and a rate limit. Tier 3: acts without a card. Not switched on. Autopilot is coming, and until it arrives no tool runs at this tier. When it does, a tier 3 tool will run with no card only inside a play an admin has approved, with a named owner, an alert if its behaviour drifts, a red-team pass before it is switched on, and a kill switch. The tiers follow the thinking behind the EU AI Act, which asks for more care where an AI system can do more harm: the more a system can act on its own, the more oversight, record-keeping and ways to stop it are needed. Our design is aligned with that thinking. We do not claim certification or legal compliance with the Act. It describes how we build, and the binding terms are in your agreement. 06 · Where it lives ## Where it lives. Every exception named. Your workspace, your records and the library are stored in Stockholm (eu-north-1). Some services run in the United States under Standard Contractual Clauses: sign-in (WorkOS), web search (Serper), connected apps (Composio) and the AI fallback (Anthropic). Annex B says what each one receives. Reasoning runs in the EU by default, on Amazon Bedrock EU inference profiles, within EU regions. Data is encrypted in transit with TLS 1.2 or better and at rest with AES-256. Secrets stay server-side, never handed to a browser. One caveat, stated plainly: some inference runs outside the EU under Standard Contractual Clauses. That covers live web search, which the EU region does not offer, streamed responses, which our EU integration does not yet support, and fallback when the EU route is unavailable. No customer records are stored there. Every processor is named and versioned in the data processing agreement and sub-processor list , and that list is the authoritative one. Kvasir does not speak aloud today. No voice-synthesis service receives anything, and none is named in Annex B. Records reach only the services named in Annex B, and only as each row says. Meeting capture runs only after a seller switches listening on, and never without consent recorded. Its processing region is not pinned yet. Annex B says so. Google favicon service: receives a company's website domain from our server, to draw its logo. Never a person, never who looked. 07 · Objection and erasure ## The route, in plain words. ### If you want out, one email does it. Write and say what you want: access to what we hold, a correction, an objection to the processing, or erasure. We answer within one month, as the law requires, and sooner in practice. An erasure is a suppression as well as a delete. The record is removed and the identifier is held on a suppression list so the next load of the register does not quietly bring it back. That is the only thing that survives an erasure. For a security issue, give us reasonable time to fix it before public disclosure. We will tell you what we found and when it was closed. Site visitors ## Companies that read your site. Never people. A seller can add one line to its own site, forgeby.com/v.js, and learn which companies read it. Here is all it does. - The script sets no cookie, stores nothing in the browser and reads nothing about the device. It sends the page (never the query string), a site key and the time. Never the referrer. - Do Not Track and Global Privacy Control stop it. With consent mode on, the default for sites in the EU, it sends nothing until the visitor says yes. - We use the visitor's network address once, in memory, to find its network block and look up, in public internet registry data, which organisation holds it; registries only ever see the block. Our code keeps no copy of the address. Like any website, our hosting provider processes the connection to deliver the request, under its data processing agreement with us. - Only an organisation's own network is matched, and only to a company in our own library with a known headcount of at least 10. Home broadband, mobile networks, VPNs, cloud hosts, public wifi, sole traders and companies of unknown size resolve to nothing. - We keep the company, the pages and the hour of the visit for 90 days. Nothing finer than the hour, and no person. - Careers and jobs pages never count, a seller's own staff are left out, and anything on a seller's never-list is never filed. - Any organisation can ask to be left out of every seller's list at forgeby.com/visitors/opt-out . A link goes to a role mailbox at its domain, and only that link leaves it out; then what was filed for it is deleted. This feature is in review with counsel before launch. This entry changes on the day it does. 08 · What we do not claim ## GDPR-aligned. Not ISO certified. Forgeby is a Swedish company built to GDPR. The proof is not a seal, it is the machinery, and every piece is public: - Every sub-processor named in Annex B, with its region and its date. - The Article 14 notice , in plain language, with an absolute one-email opt-out. - Your rights answered in 14 days, half the month the law allows ( privacy ). - National suppression registers honoured in the data itself: reklamspärr, NIX, reklamebeskyttelse. - No scraper of ours runs against a network behind a login, and we do not log in to or crawl a social network. Person data comes from a provider named in Annex B, licensed under contract; from public search results, including public professional profiles those results return; or from our founder's own professional network export. We can tell any person which of the four categories their record came from. - The data processing agreement and its full sub-processor table, published. - Nothing sold, no ad trackers, and no consent banner because nothing consent-gated loads ( cookies ). ISO 27001 is on the roadmap and we are not certified today. We do not claim certifications we have not earned. This page changes on the day that does. The fastest way to judge this is to try it on your own accounts. Start free. This page describes our posture in good faith. It is not a contract. The binding terms are in your agreement and in the data processing agreement. --- # The crawler > What it reads, and how to keep it out. > Source: https://forgeby.com/crawler.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. # The Forgeby crawler If you found something beginning forgeby- in your access log, this page tells you exactly what it is, what it took, and how to stop it. If you would rather just block us, skip to how to stop us . One line stops all of it. ## Who is running it Two companies appear if you look this up, so here is the honest split rather than a single name that will not match what you find. We build account memory for B2B sellers and go-to-market teams. Write to privacy@forgeby.com about anything on this page and a human will answer. If you have already raised it with Amazon, it reaches us either way. The address you saw · Novalo Technologies AB holds the AWS account the crawler runs in, so a WHOIS or abuse lookup on 51.21.44.111 leads to Amazon and then to Novalo. Novalo is an AWS consulting partner and provides the infrastructure. · The crawler itself · Zmart Com West AB (org.nr 559019-9161), trading as Forgeby , Sweden, operates it and decides what it does. For anything about the data it holds, Forgeby is the controller under the GDPR. ## How to recognise it Seven of our agents read websites, and every agent we run is named forgeby- something. That is deliberate, so that a single robots.txt line covers all of them and you never have to keep a list up to date. Anything not on this list is not us. forgeby-ownsite · Reads the pages where a company describes itself and its people: an about page, a team page, a contact page. · forgeby-techdetect · Reads your homepage once to record which web technologies it runs on. · forgeby-domainfind · Checks whether a website belongs to a company we already hold a record for. One request, and it stops as soon as the answer is clear. · forgeby-domainfill · The same check, for companies outside the Nordics. · forgeby-chatdetect · Reads your homepage to record which chat or assistant widget it runs, and at most two further pages that your homepage links to . · forgeby-cloudsig · Reads your homepage once to record which cloud your public assets are served from. · forgeby-origin · The same check, looking at where your site is hosted. Nine more exist, for completeness, though none of them browses a website the way the seven above do. forgeby-verify makes a single request to a page we already hold a link to, purely to check that the link still resolves. forgeby-msdocs , forgeby-brreg , forgeby-stats , forgeby-registry-load , forgeby-estate and forgeby-ct , forgeby-awsdocs and forgeby-webfetch only ever call published APIs and open datasets: Microsoft's documentation, the Norwegian company register, the Nordic statistics offices, the Estonian, French and UK company registers, a public address-to-network mapping table and a public certificate-transparency log. They will not appear in your logs unless you are one of those. All of them answer to the same User-agent: forgeby line. Full user agent · Mozilla/5.0 (compatible; forgeby- name /1.0; +https://forgeby.com/crawler.html) · Source address · 51.21.44.111 , and only that address. Anything else claiming to be us is not us. · Requests · One at a time per site, at least 1.5 seconds apart. That 1.5 seconds is a floor: if your robots.txt sets a longer Crawl-delay , we use yours. · Depth · forgeby-ownsite reads your homepage plus at most four pages that your homepage links to ; forgeby-chatdetect your homepage plus at most two. The rest read a single page. None of them constructs a URL: we follow only links you have published. This was not true of forgeby-chatdetect before 26 August 2026. See “Changes we made on 26 August 2026” below. · If we miss twice · Two failed requests in a row and the agent leaves your site alone for the rest of that run, whatever the reason for the failure. ## What it reads, and why Public pages where a company describes itself and its people: an about page, a team page, a contact page. We record the business contact details a company has chosen to publish about its own staff, so that a B2B seller looking for the right person to speak to can find one. Everything we hold, and the legal basis for it, is set out in the privacy notice , including how any individual can object. The notice is published in the languages the people in it read, because a notice somebody cannot read is not a notice: English · Svenska · Norsk · Dansk · Suomi · Français · Nederlands ## What they do not do - They do not request URLs you have not linked. They do not guess paths. - They do not touch anything behind a login, and they never attempt a CAPTCHA. - They do not ignore robots.txt , and they obey Crawl-delay where you set one. - They do not fetch anything at all from a domain on our exclusion list, robots.txt or no robots.txt. - They do not collect consumer or private-individual data. Business roles only. - They do not resell your page content. We keep contact details, not your copy. ## How to stop us Any one of these works, and none of them needs to involve us. One line in robots.txt stops every agent we run, now and in future: ``` User-agent: forgeby Disallow: / ``` Because every agent is named forgeby- something, that prefix matches all of them, including any we add later. If you would rather stop just one, name it in full: ``` User-agent: forgeby-ownsite Disallow: / ``` We re-read robots.txt on every visit, so a change takes effect immediately, and we treat a disallow as final rather than as something to work around. We obey Crawl-delay where you set one, and it can only slow us down, never speed us up. You can also block 51.21.44.111 at your edge, or mail privacy@forgeby.com with your domain and we will add it to a permanent exclusion list that every agent checks before it requests anything. It covers your subdomains too. No reason required, and we do not ask for one. ## Changes we made on 26 August 2026 On 26 August we were reported a second time. The cause was an agent this page never listed. One of our own crawlers was not named forgeby- anything, so the opt-out rule above could not stop it. It identified itself as AlloyChatDetect/1.0 , carried no link back to this page, did not request robots.txt at all, and asked for four guessed paths ( /kontakt , /kundservice , /support and /contact ) on sites that had none of them. If you blocked User-agent: forgeby and it still arrived, that is why. It was our defect and we are sorry. Everything this page said was true of the crawlers it listed and untrue of that one. It ran on a separate part of our system that the changes of 4 and 5 August never reached, and we had not enumerated that part before describing our crawling as a whole. That is the real fault, and it is ours. We have stopped it; added the reporting sites to a permanent exclusion list; renamed every agent we run to forgeby- something, so the single rule above now genuinely covers all of them; and removed the guessed paths, so it follows only links your homepage publishes, at most two of them. The list above is no longer a description of some of what we run. It is all of it. ## Changes we made on 4 and 5 August 2026 On 4 August we were reported for requesting a short list of guessed paths on sites that did not have them, which produced a burst of 404s and looked like scanning. That was our error, not a grey area. We removed path guessing entirely: the crawler now requests only URLs a site has itself linked. It also stops visiting a host after two consecutive failed requests, and the minimum gap between requests went from one second to 1.5. On 5 August we found that the opt-out rule this page told you to write did not work. The rule was correct; our software was not reading it correctly, and only a blanket User-agent: * was actually stopping us. If you added a forgeby-ownsite rule before 5 August and wondered why we kept arriving, that is why. It was our defect and we are sorry. It is fixed, we have verified it against a real robots.txt , and the single User-agent: forgeby line above now genuinely stops all four agents. Two other things changed the same day. Our other agents previously identified themselves with names that did not match this page and did not read robots.txt at all; all four now do both. And the permanent exclusion list described above is now a real list that every agent checks before every request, rather than a promise we would have had to keep by hand. We are sorry for the noise in your logs. --- # MCP > The Forgeby MCP server, documented: transport, auth, tools, and the limits. > Source: https://forgeby.com/mcp.html > Figures on the landing follow the nightly count and carry the date they were counted. Figures on > the static pages are snapshots and are not re-counted. A number here was true when it was > counted, not when you asked. # Kvasir over MCP. One endpoint at /api/mcp . Seventeen reads run on your workspace’s accounts. Fourteen writes return an approval link and do not run. Nothing is sent. This page is the documentation the server itself points at when it answers you. ``` https://forgeby.com/api/mcp ``` Protocol version 2025-03-26. Machine-readable server card at /.well-known/mcp/server-card.json, written by hand and last checked against the server’s own initialize response on 2026-09-22. ## A seat. The handshake stays open. initialize and ping answer without a token, so a client can complete the protocol handshake and read a proper error instead of hitting a dead socket. Every method that returns data needs a seat: an AuthKit JWT or a session bearer on this Forgespace. ``` {"jsonrpc":"2.0","id":1,"error":{"code":-32001, "message":"signed out"}} ``` Error -32001 means signed out. There is no zone grant on this door. There is no 14-day window. Every seat is free. See pricing. ## Seventeen reads. Fourteen writes that wait. Reads: who_to_call , whats_changed , prep_meeting , query_corpus , account_contacts , my_network , due_draft , account_context , pipeline , intent_watch , can_contact , champion_check , found_revenue , accounts_changed , kvasir_learned , what_kvasir_learned , decision_record . Writes: desk_act , network_campaign , enrich_contact , find_people , reverse_email , find_companies , remember , engagement_update , book_meeting , post_slack , take_due , set_never_list , send_mail , and schedule return an approval link and do not run. Resources and prompts list empty. The kernel is the same one the desk uses. Tool · Arguments · Returns · who_to_call · days, limit, industry · Who to call today and why, from public signals on your workspace’s accounts. · whats_changed · company_id, domain, name, days · What changed at one company already on the shelf, from official public sources. News is no source until a feeder exists. · prep_meeting · match, days_ahead · Prep from the seller’s own calendar and mailbox, read only. Reports zeros. · query_corpus · name_like, domain, country, limit · Look up a company on the measured shelf. count is the page size, never a market total. · account_contacts · company_id, domain, limit · People already held on one company. LinkedIn® is the URL we already hold. · my_network · q, limit, team_account · People on the shared graph and your own Connections.csv. With team_account, who on your team knows people at an account you work, as paths only. · due_draft · enrollment_id · The next due email: address, subject, and body. Does not send. · account_context · company_id · One sourced picture of a company already on the shelf. Missing parts are named as gaps. · pipeline · company_id, stage, limit · Open engagements this seat can see. Does not name a CRM the workspace has not connected. · intent_watch · phrase · Sentences already on the record that contain a phrase. Does not send. · can_contact · contact_id, email, channel · Whether this seat may contact one person, and why. A missing part is a gap, not permission. · champion_check · company_id · Contacts whose status or title says they left or moved. A missing status is a gap. · found_revenue · days, limit · Leads with a public signal and no follow-up on the desk. Does not send. · accounts_changed · days · What changed across the accounts this seat can already see. News is no source until a feeder exists. · kvasir_learned · · What Kvasir learned this week from decision records. · what_kvasir_learned · · What Kvasir learned this week. Same as kvasir_learned. · decision_record · pending_id, company_id · One decision record for this seat: suggested, changed, decided, happened, learned. · desk_act · enrollment_id, note · An approval link. Does not mark the step done. · network_campaign · name, q, offer · An approval link. Does not create the campaign. · enrich_contact · contact_id, want · An approval link. Does not run the lookup. · find_people · domain, titles, mobiles · An approval link. Does not run the search. · reverse_email · email · An approval link. Does not run the lookup. · find_companies · domain, name · An approval link. Does not run the search. · remember · fact, action, kind · An approval link. Does not keep the sentence. · engagement_update · id, stage, next_action, note · An approval link. Writes this desk only after accept. Does not name a CRM. · book_meeting · title, start, end · An approval link. Does not book. · post_slack · channel, text · An approval link. Does not post. Teams is not this tool. · take_due · enrollment_id, to, subject, text · An approval link. Does not send the due email. · set_never_list · forbidden_senders, discount_floor · An approval link. Does not keep the never-list. · send_mail · to, subject, text · An approval link. Does not send. · schedule · what, when, id · An approval link. A reminder on the desk, not a booking. ## The limits are in the protocol, not the prose. ### Nothing is sent The seller sends, files, and sits in the room. This surface never sends a customer a message. ### A write returns an approval link Every write files a pending row and returns a link. It does not run. It does not send. The seller accepts or declines the card on the desk. Partner Central submit is not a tool. Teams does not post from here. ### LinkedIn is the URL we already hold We do not fetch LinkedIn.com. People come from the book, the mailbox, and a Connections.csv the seller uploaded. ### News has no feeder whats_changed reads official public signals already on file. News says no source until a feeder exists. The same statements sit in initialize : Kvasir is a sales coworker. These tools read your workspace’s own accounts. A write returns an approval link and does not run. Nothing is sent. ## Claude today. ChatGPT, Codex and Cursor next. ``` { "mcpServers": { "forgeby": { "type": "http", "url": "https://forgeby.com/api/mcp" } } } ``` On claude.ai and Claude Desktop: open Customize, then Connectors. Add a custom connector. The URL is https://forgeby.com/api/mcp . Sign in with the Forgeby seat. Team and Enterprise: an Owner adds it under Organization settings, then each seat clicks Connect. Claude Code: `claude mcp add --transport http forgeby https://forgeby.com/api/mcp`. Claude is tested end to end. ChatGPT, Codex and Cursor take the same URL and are testing before launch. A session bearer still works for a client that cannot finish that sign-in. Also here for machines: /openapi.json · /llms.txt · /llms-full.txt · this page as Markdown . The AI at the front of this product is Kvasir, openly an AI, with a signed identity passport .