The principle
Use Purceivo to decide what your firm should bid on. Do not use it to
resell our judgement, to harm the procurement process, or to damage the
service for everyone else.
Everything below follows from that sentence. If something is not listed
but plainly violates it, treat it as covered.
Do not resell the judgement layer
You may use surfaced items, rationales and the withheld record freely
inside your firm and with your clients and teaming partners. You may
not repackage them into a product, feed, newsletter or dataset offered
to others, whether free or paid, and you may not scrape the interface
to build one.
Why: the underlying solicitations are public and we
claim nothing over them. The scoring, the rationales and the withheld
record are what we actually make. Reselling those is taking the only
thing there is to take.
Do not use it to corrupt a procurement
You may not use the service to coordinate bids with a competitor, to
allocate markets or rig prices, to conceal a conflict of interest, to
obtain or traffic in source selection information or a competitor's
proprietary information, or to prepare a submission you know to be
materially false.
Why: our users bid for public money. Bid rigging and
procurement fraud are crimes, and a tool that made them easier would
deserve the liability it earned. This is the one rule where we will
suspend first and discuss afterwards.
Do not put in what you do not have the right to put in
Do not upload or paste a third party's confidential or proprietary
material without permission, personal data about people who have not
agreed to it, classified or export-controlled information, or anything
subject to a restriction you are not authorised to waive.
Why: content you supply is transmitted to our model
provider to be scored (see
Privacy, § 05). You cannot
consent on someone else's behalf to that, and classified or
export-controlled material must not transit a commercial API at all.
Do not attack or overload the service
No probing, scanning or penetration testing without written permission;
no attempt to access another firm's data; no circumventing
authentication, rate limits, role restrictions or spend caps; no
deliberate overload; no uploading malware; no interfering with anyone
else's use.
Why: one shared corpus and one shared database serve
every firm. Testing your creativity against them is testing it against
other people's businesses. If you want to test our security, ask first. See Security, § 06.
Do not share seats or hoard keys
A seat belongs to one person. Do not share credentials between
colleagues, and remove seats when people leave. Treat API keys as
secrets: do not commit them to a repository, paste them into a ticket,
or embed them in client-side code.
Why: the audit log attributes actions to accounts.
Shared credentials make it useless precisely when it matters, which is after something has gone wrong.
Automated access
Use the API for automation. Do not drive the web interface with a script. Respect rate limits and the documented pagination. If you need
a higher limit for a legitimate reason, ask instead of working around
it.
What happens if you breach this
Depending on severity we may contact you, rate-limit or restrict a
feature, suspend an account or key, or terminate the firm's access.
Where circumstances allow, we will tell you what happened and give you
a chance to put it right first. For the procurement-integrity and
security rules, we may act immediately and explain afterwards, and we
may be obliged to report the matter.