Legal
Estimate API Terms
Version: 2026-10-14
Effective: 2026-10-14
Hometown Workforce, LLC, 2519 Provence Pl, Biloxi, MS 39531, USA. Contact: legal@hometownworkforce.com
1. About these Terms
1.1. These Estimate API Terms of Service (the "Terms") are a contract between Hometown Workforce, LLC ("Hometown", "we", "us"), and the business that opens a developer account ("Customer", "you").
1.2. These Terms cover the Estimate API at https://api.wfskills.com/v1, the developer portal, the documentation at https://developers.wfskills.com, the sandbox, the SDKs and sample code we publish, and the Records add-on (together, the "Service").
1.3. These Terms include, by reference: the Data Processing Agreement at https://wfskills.com/legal/dpa (the "DPA"), the subprocessor list at https://wfskills.com/legal/subprocessors, the pricing page and the Documentation. Together they are the "Agreement".
1.4. You accept the Agreement when an authorized person checks the acceptance box and clicks the button in the developer portal. We record the version accepted, the date and time, the user who accepted and the IP address.
1.5. The Service is for businesses only. The person who accepts confirms that they have authority to bind the business. Do not use the Service for personal, family or household purposes.
1.6. The Hometown Workforce Terms of Service for the website and mobile apps do not apply to the Service.
2. Definitions
2.1. "API key" means a secret credential for the Service. Test keys start with hw_test_. Live keys start with hw_live_.
2.2. "Credits" means the prepaid units that live requests consume, as listed on the pricing page.
2.3. "Customer Data" means Input, Output and Records.
2.4. "Documentation" means the guides, reference and policies at https://developers.wfskills.com.
2.5. "End Customer" means a person or business that receives services from you and whose data you send to the Service.
2.6. "Input" means the text, photos, addresses, messages and other data you send to the Service.
2.7. "Output" means the estimates, scopes, steps, prices and other results the Service returns to you.
2.8. "Personal Data" means information about an identified or identifiable natural person.
2.9. "Records" means the data you store with the Records add-on.
2.10. "Usage Data" means metadata about your use of the Service, such as request counts, routes, status codes, latency, Credits used and error codes. Usage Data does not include the content of Input, Output or Records.
2.11. "Your Application" means the software or service in which you use the Service.
3. Account and API keys
3.1. You must give accurate account, billing and tax information and keep it up to date.
3.2. A live key requires a verified email address, a phone number on the account, a payment method saved through Stripe and a password on the account.
3.3. Keep API keys secret. Use them only on servers you control. Do not put them in mobile apps, browsers or public code repositories.
3.4. You are responsible for all use of your keys until you revoke them. If a key is exposed, revoke or rotate it in the portal at once and tell us.
3.5. We store only a hash of each key. We cannot show a key again after we create it.
3.6. You will not buy, sell, lend or share API keys with any third party.
3.7. You are responsible for the people you give access to your account. We recommend two-factor authentication for every user.
4. Test mode and live mode
4.1. Test keys return sample responses from a fixed sandbox. Test requests do not call an AI model and do not consume Credits.
4.2. Sandbox responses are examples. They are not estimates. Do not show them to End Customers as estimates.
4.3. Do not send real Personal Data in test mode. If you do, the DPA applies to it.
4.4. Live keys produce real estimates and consume Credits.
4.5. When the pricing page offers a free monthly allowance of live Credits, it requires a verified email, a phone number on the account and a saved card. Free Credits expire at the end of each calendar month. We may change or end the free allowance with 30 days' notice.
5. License to use the Service
5.1. Subject to the Agreement, we grant you a non-exclusive, non-transferable right during the term to use the Service, to integrate it into Your Application, and to make Output available to your End Customers.
5.2. Your contractors may use the Service only for you and under the Agreement. You are responsible for them.
5.3. SDKs and sample code are licensed under the license file in each package. Where a package has no license file, these Terms apply.
5.4. We keep all rights not granted in the Agreement.
6. Acceptable use
You will not, and will not allow anyone to:
6.1. break any law or violate the rights of others;
6.2. scrape, crawl or harvest data from wfskills.com, its directory, its marketplace, its service pages or any other Hometown site, except through the API as documented;
6.3. use the Service or any Output to develop, train, fine-tune or improve an AI model, a pricing dataset or a service that competes with the Service;
6.4. reverse engineer the Service, or try to extract its prompts, models, rate tables or weights, except where law allows this despite this restriction;
6.5. resell the Service or offer it to third parties as a stand-alone or white-label API without our written consent. Embedding Output in Your Application is allowed;
6.6. get around rate limits, caps, IP allowlists, moderation or security controls, or open several accounts to get more free Credits;
6.7. scan, probe or test the security of the Service without our written permission, or interfere with the Service;
6.8. send malware or harmful code;
6.9. send health, genetic or biometric data, government identification numbers, payment card or bank account numbers, data about racial or ethnic origin, religion, sex life or criminal records, or data about children under 16;
6.10. send images of people when the job can be shown without them, or any sexual content involving minors. We report such content to the authorities;
6.11. use the Service for unlawful services, including: (a) home work that requires a license you or your contractors do not hold; (b) deceptive pricing, bait-and-switch offers or fraud, including insurance fraud; (c) price-fixing or bid-rigging with competitors; (d) pricing or service decisions based on a protected characteristic; (e) messages to End Customers that break telemarketing, spam or privacy laws;
6.12. present Output as a binding quote, an appraisal, an insurance adjustment, an engineering opinion, a code-compliance opinion or the work of a licensed professional, unless a qualified person has reviewed it and the law allows it;
6.13. use the Service from a sanctioned country or for a restricted party (Section 27);
6.14. create accounts by automated means or misrepresent your identity.
7. AI estimates
7.1. An automated system produces Output. It uses AI models and regional rate tables. Output can be wrong, incomplete or out of date.
7.2. Output relies only on the Input. The system cannot see hidden conditions, local codes or the actual site.
7.3. Output is assistance. It is not a binding quote, an offer, an appraisal or professional advice. The business that does the work sets the final price and scope after it inspects the job.
7.4. You must review Output before you use it or show it to anyone. You are responsible for the prices and quotes you give, and for the laws that apply to them.
7.5. Where law requires it, you must tell End Customers that they are dealing with AI or that content was generated by AI. Every live estimate the Service returns is generated by AI.
7.6. Output may not be unique. Other customers may receive similar Output for similar Input.
7.7. We screen Input with automated moderation. The Service may decline a request. A declined request is charged only as the pricing page states.
8. Customer Data and privacy
8.1. You own Customer Data. You grant us a worldwide, non-exclusive, royalty-free license to host, copy, transmit and process Customer Data. This license covers only providing, securing and supporting the Service, preventing abuse, complying with law and anything else the DPA allows.
8.2. For Personal Data in Customer Data, you are the controller and we are your processor. If you act for another business, you are the processor and we are your subprocessor. The DPA governs this processing.
8.3. We are an independent controller of account, billing, authentication, security and Usage Data. Our privacy notices describe that processing.
8.4. You are responsible for having a lawful basis, giving notices and getting consents before you send data to us. This includes photos and the processing of data by AI providers in the United States.
8.5. You are responsible for answering requests from your End Customers. The Service gives you tools to do so (Section 8.7).
8.6. We keep data for the following periods: (a) request and response bodies, and estimate inputs and outputs: for the retention period you set, from 0 to 30 days. The default is 30 days; (b) photos: never stored. We keep only the SHA-256 hash, the file type and the size of each image; (c) text that the Service builds and sends to the AI model: never stored; (d) request metadata without content (route, status code, Credits, latency and a hash of the IP address): 13 months, for billing, security and disputes; (e) idempotency results: 24 hours; (f) Records: until you delete them, or as Section 10.6 and Section 26 state; (g) backups: up to 7 days after deletion from live systems.
8.7. You can delete an estimate with DELETE /v1/estimates/{id}. You can set retention to 0 days. You can export or delete Records.
8.8. We send Input to the AI provider named in the subprocessor list. We ask that provider not to store requests. Under its API terms it does not use API data to train its models, and it may keep requests for up to 30 days only to monitor abuse.
9. Our commitments about your data
9.1. We will not use Customer Data to train or fine-tune any AI model, ours or anyone else's.
9.2. We will not use Customer Data, your Confidential Information or Usage Data that identifies you to: (a) build or market a product that copies Your Application; (b) contact or solicit your End Customers, including through our marketplace; (c) sell or share data with third parties.
9.3. We may use Usage Data to run, bill, secure and improve the Service and to set Credit weights. We may also use aggregated statistics that do not identify you or any person and that do not contain the content of Input, Output or Records.
9.4. Our personnel access Customer Data only to give support you request, investigate abuse or security incidents, or comply with law.
9.5. If an authority asks us for Customer Data, we will notify you before we disclose it, unless the law forbids it. We will disclose only what the law requires.
10. Records add-on
10.1. The Records add-on is an optional paid subscription. It lets you store End Customer records (name, phone, email, address and notes) and other collections through /v1/customers and /v1/records.
10.2. We encrypt phone and email fields at the application level with AES-256.
10.3. You decide what to store. You must have the legal right to store it. We process Records as your processor under the DPA.
10.4. The pricing page lists the included quota and the price for extra records. We measure the highest daily count of active records in each month.
10.5. You can export Records as JSON at any time. You can delete one record or all of them.
10.6. If the add-on ends, keys with Records scopes return 403. We keep the Records for 30 days so you can reactivate or export them. After that we delete them.
10.7. The Records add-on is not a backup. Keep your own copy of data you need.
11. Credits, plans and billing
11.1. Prices are on the pricing page in USD, EUR, GBP and MXN. Your currency is fixed when we create your billing profile.
11.2. Payments go through Stripe Checkout and Stripe Billing. Stripe processes card data. We do not receive full card numbers.
11.3. Each type of live request consumes the number of Credits that the pricing page lists. The Service holds Credits when a request starts and charges them when it answers. If a request fails because of an error on our side, we release the Credits.
11.4. Credit packs expire 12 months after purchase unless the pricing page states a longer period. Credits included in a plan expire at the end of the billing period. Free Credits expire at the end of the calendar month. We spend the Credits that expire first.
11.5. Credits have no cash value. They are not money or stored value. They cannot be transferred or exchanged for cash.
11.6. A monthly plan renews each month until you cancel it in the portal. A cancellation takes effect at the end of the current period. We bill usage above the included Credits in arrears at the metered price.
11.7. Automatic top-up is optional. When you turn it on, you authorize us to charge your saved payment method for the pack you chose each time your balance falls below your threshold. You can turn it off at any time.
11.8. You may set a monthly spending cap. When you reach it, live requests return 402 monthly_cap_reached and are not charged. The cap resets on the first day of the month in your account time zone.
11.9. We give 30 days' notice before we increase the price of a plan or the add-on, change the Credits per request type, or reduce the free allowance. New pack prices apply only to future purchases.
11.10. Invoices and receipts are available in the portal.
11.11. You must raise a billing dispute within 60 days of the charge.
11.12. If you turn on automatic pausing, the Service may pause keys when usage looks unusual. We notify you, and you can resume the keys in the portal.
12. Taxes
12.1. Prices do not include taxes. Where we are registered, we calculate and collect sales tax, VAT, GST or IVA with Stripe Tax, based on your billing address and tax ID.
12.2. Where a reverse charge or self-assessment applies, you account for the tax. This includes business purchases in the EU and the UK, and IVA on imported services in Mexico while we are not registered there. The invoice states when this applies.
12.3. If the law requires you to withhold tax from a payment to us, you will increase the payment so that we receive the full amount. This does not apply where a tax treaty reduces the withholding and you give us the documents.
12.4. You are responsible for taxes that result from wrong tax information you give us.
13. Failed payments
13.1. If a payment fails, your account becomes past due. We notify you and Stripe retries the payment.
13.2. While the account is past due, the API keeps working.
13.3. If payment fails three times within 14 days, we suspend API access for the account. We restore it when you pay the open invoice.
13.4. If you dispute a charge with your bank (a chargeback), we may suspend the account until the dispute is resolved.
14. Refunds
14.1. Prepaid Credits and subscription fees are not refundable, except: (a) where the law requires a refund; (b) when we made a billing error; (c) when we end the Agreement without cause or discontinue the Service (Sections 16.7 and 25.3); (d) when you end the Agreement because you reject a change under Section 17.5, or object to a subprocessor under the DPA; (e) when you end the Agreement because of our material breach that we did not cure.
14.2. In cases (c), (d) and (e), we refund the unused paid Credits that have not expired and the unused part of prepaid plan and add-on fees.
14.3. We refund to the original payment method in the original currency. We never refund free or promotional Credits.
15. Rate limits
15.1. The Documentation lists the limits per minute, per day and per key, and the size limits. Responses report the limits in headers. A request over a limit returns 429.
15.2. You may ask for higher limits.
15.3. We may lower limits for an account for a short time to protect the Service from an emergency. We will tell you why.
15.4. We give 30 days' notice before we lower the default limits, except in an emergency.
16. Changes to the Service, versions and deprecations
16.1. The API uses /v1 and a Hometown-Version date header. Your account is pinned to the version in effect when you created your first key. You can choose another version in each request.
16.2. We may make non-breaking changes at any time. These include new endpoints, new optional fields, new response fields and new error codes. The Documentation defines what counts as breaking.
16.3. We give at least 90 days' notice before we make a breaking change, retire a version or retire an endpoint or feature. We send the notice by email to the account owner and the billing contact, and we publish it in the changelog. We support each version for at least 12 months after its release.
16.4. We may give shorter notice only when we must fix a security vulnerability, comply with law or an order, or replace a subprocessor that stopped working without enough notice to us. In those cases we give as much notice as we can and explain why.
16.5. Features marked beta may change or end without the notice in Section 16.3.
16.6. We may change the AI models and rate tables behind the Service to keep or improve estimates. This is not a breaking change if the API contract stays the same. Output may vary after such a change. We note model changes in the changelog.
16.7. If we discontinue the Service, we give at least 90 days' notice and the refund in Section 14.2.
17. Changes to these Terms
17.1. We may update the Agreement. We publish each version with its date and keep earlier versions available on request. We email the account owner and the billing contact.
17.2. For a material change that is adverse to you, we give at least 60 days' notice before it takes effect.
17.3. A change required by law or for security may take effect sooner. Other changes take effect on the date the new version states. Subprocessor changes follow the DPA.
17.4. To keep using live keys after a new version takes effect, an authorized user must accept it in the portal. Until you accept it, the previous version applies to you. If you have not accepted it 30 days after it takes effect, live requests return 403 terms_not_accepted until you accept. Test keys keep working, and your data stays.
17.5. If you do not agree with a change, you may end the Agreement before the change takes effect or before your live keys stop. You then get the refund in Section 14.2.
17.6. A change does not apply to a dispute that arose before it took effect.
18. Intellectual property
18.1. We own the Service, the Documentation, our models, prompts and rate tables, and Usage Data. You get no rights except those in the Agreement.
18.2. As between you and us, you own the Output. We assign to you any rights we have in the Output. Section 7.6 still applies, and we do not promise that Output can be protected by law.
18.3. If you send us feedback, we may use it without any duty to you.
18.4. You may say that Your Application uses the Service. You may use our names and logos only as our brand guidelines allow.
18.5. We will not name you as a customer without your written permission.
19. Confidentiality
19.1. "Confidential Information" means non-public information that one party gives the other and that a reasonable person would treat as confidential. This includes Customer Data, API keys, non-public pricing and security information.
19.2. Information is not confidential if it is public through no fault of the receiving party, or if the receiving party already knew it, received it lawfully from someone else, or developed it independently.
19.3. Each party will use the other's Confidential Information only for the Agreement, and will protect it with at least reasonable care.
19.4. Each party will disclose the other's Confidential Information only to its staff, contractors and advisers who need it and who are bound by confidentiality duties.
19.5. A party may disclose Confidential Information when the law requires it. It will give prior notice where the law allows.
19.6. These duties last for 5 years after the Agreement ends, and for as long as a trade secret remains a trade secret.
20. Security
20.1. We maintain the security measures in Annex II of the DPA.
20.2. You secure your systems, your keys and your webhook secrets, and you verify webhook signatures.
20.3. We notify you of a personal data breach as the DPA states.
20.4. Report security problems to legal@hometownworkforce.com.
21. Warranties and disclaimers
21.1. Each party confirms that it has authority to enter into the Agreement and will comply with the laws that apply to it.
21.2. We warrant that the paid live Service will perform materially as the Documentation describes. If it does not, tell us within 30 days. Your remedy is that we fix the problem or return the Credits for the affected requests.
21.3. You warrant that you have the rights, notices and consents needed for the Customer Data you send.
21.4. Except as Section 21 states, the Service, Output, the sandbox, free Credits and beta features are provided "as is" and "as available". We disclaim all other warranties, including merchantability, fitness for a particular purpose, title, non-infringement and accuracy. We do not warrant that Output is correct or complete, or that the Service will be uninterrupted or free of errors. There is no service level agreement unless we sign one with you.
22. Limitation of liability
Please read this section carefully. It limits each party's liability.
22.1. Neither party is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, goodwill or data, even if it was told that they were possible.
22.2. Each party's total liability for all claims under the Agreement is limited to the greater of: (a) the amounts you paid us for the Service in the 12 months before the event that gave rise to the liability; or (b) 100 US dollars.
22.3. Sections 22.1 and 22.2 do not limit: (a) your payment obligations; (b) either party's indemnity obligations; (c) your breach of Section 5 or Section 6; (d) liability for gross negligence, willful misconduct or fraud; (e) liability that the law does not allow the parties to limit.
22.4. Both parties are businesses. The prices reflect this allocation of risk.
22.5. The DPA is subject to this Section, except where the Standard Contractual Clauses or the law require otherwise.
23. Indemnification
23.1. We will defend you against a third-party claim that the Service infringes a patent, copyright or trademark, or misappropriates a trade secret, in the United States, the European Union, the United Kingdom or Mexico. We will pay the damages and costs awarded against you, or a settlement we agree to. (a) This does not cover claims caused by Output, Customer Data, third-party software, your changes, combinations with things we did not provide, free Credits or beta features. (b) To resolve such a claim, we may get you the right to keep using the Service, modify it so it no longer infringes, or end the affected part and refund unused prepaid amounts.
23.2. You will defend us against third-party claims that arise from: (a) Customer Data, including your lack of rights or consents; (b) Your Application and your dealings with End Customers, including the prices and quotes you give and the work done; (c) your breach of Section 6 or of the law. You will pay the damages and costs awarded against us, or a settlement you agree to.
23.3. The party that asks for defense must notify the other promptly, let it control the defense and cooperate. Neither party may settle a claim in a way that admits fault for the other party without its consent.
23.4. Section 23 is the only remedy for third-party intellectual property claims.
24. Suspension
24.1. We may suspend all or part of the Service, such as one key or live mode only, if: (a) law or an order requires it; (b) there is a security emergency or a threat to the Service or to others; (c) you materially breach Section 6; (d) payments fail as Section 13 describes; (e) Section 27 applies; (f) usage shows fraud, or anomalies that you chose to pause on; (g) you did not accept updated terms within the time in Section 17.4.
24.2. We keep a suspension as narrow and as short as possible. We notify you before we suspend when we can, and otherwise right after, with the reason. We restore access promptly once the cause is resolved.
24.3. A suspension is not termination. Fees for usage before the suspension remain due.
25. Term and termination
25.1. The Agreement starts when you accept it. It continues until one of the parties ends it.
25.2. You may end the Agreement at any time by notice to legal@hometownworkforce.com or by closing your account. Refunds follow Section 14.
25.3. We may end the Agreement without cause only with at least 90 days' written notice. We then refund as Section 14.2 states.
25.4. Either party may end the Agreement with cause: (a) if the other party materially breaches it and does not cure the breach within 30 days after notice; (b) at once, if the other party becomes insolvent.
25.5. We may also end the Agreement at once for a serious breach of Section 6 that causes harm, for a breach of Section 27, for fraud, or if the law forbids us to continue.
25.6. We may close an account that has no paid balance and no requests for 18 months, with 90 days' notice.
26. Effect of termination
26.1. When the Agreement ends, your access ends and we revoke your keys.
26.2. Export the Records you need before the Agreement ends; we answer a request for a copy made within 30 days after the end. We delete Customer Data within 30 days after the end. Backups expire within 7 more days. We keep only what the law requires us to keep.
26.3. Amounts you owe become due. Unused Credits end, except for the refunds in Section 14.
26.4. Sections 8.6, 9, 12, 14, 18, 19, 21 to 23, 26, 29 and 31 survive termination.
27. Export controls and sanctions
27.1. You confirm that you are not located in, organized under the laws of, or ordinarily resident in a country or region under a comprehensive US embargo.
27.2. You confirm that you and your owners are not on a US, EU, UK or United Nations sanctions or restricted party list.
27.3. You will not use the Service for a prohibited end use, or make it available to a sanctioned person or country.
27.4. You may open an account only in the countries and regions that the Documentation lists.
27.5. We may suspend or end the Service at once to comply with this Section.
27.6. Each party will comply with the anti-corruption and anti-money-laundering laws that apply to it.
28. Free and test use
28.1. Test mode and free Credits are provided at no charge. Sections 21.2 and 23.1 do not apply to them.
29. Governing law and venue
29.1. The laws of the State of Mississippi, USA, govern the Agreement, without regard to conflict-of-law rules. The UN Convention on Contracts for the International Sale of Goods does not apply.
29.2. Before filing suit, the parties will try in good faith for 30 days to resolve the dispute. This does not apply to urgent injunctive relief.
29.3. The state courts located in Harrison County, Mississippi, and the United States District Court for the Southern District of Mississippi, Southern Division, have exclusive jurisdiction. Each party consents to their personal jurisdiction.
29.4. Either party may seek injunctive relief in any competent court to protect its intellectual property or Confidential Information.
29.5. To the extent the law allows, each party waives trial by jury.
29.6. Disputes under the Standard Contractual Clauses follow the law and courts that those clauses set. Nothing in this Section removes rights that the law does not allow the parties to waive.
30. Notices
30.1. We send notices to the email addresses of the account owner and the billing contact, and in the portal. A notice is given when we send it, unless we receive a delivery failure.
30.2. Send notices to us at legal@hometownworkforce.com. For a notice of breach or termination, also send a copy by mail to 2519 Provence Pl, Biloxi, MS 39531, USA. A notice to us is given on the business day we receive it.
30.3. Keep your contact emails current.
31. General
31.1. Assignment. Neither party may assign the Agreement without the other's consent. Either party may assign it without consent to an affiliate, or to a successor in a merger or a sale of the business, with notice.
31.2. Force majeure. Neither party is liable for delays caused by events beyond its reasonable control. This does not excuse payment obligations.
31.3. The parties are independent contractors.
31.4. There are no third-party beneficiaries, except the rights that the Standard Contractual Clauses give to data subjects.
31.5. We may use subcontractors. We are responsible for them. The DPA governs subprocessors.
31.6. The English version controls. We provide a Spanish version for convenience.
31.7. If a court finds a provision unenforceable, the rest of the Agreement stays in effect. A waiver must be in writing. Headings are for convenience only.
31.8. If documents conflict, this order applies: the Standard Contractual Clauses and the UK Addendum as incorporated in the DPA; the DPA, for Personal Data; a signed order form; these Terms; the Documentation and the pricing page.
31.9. The Agreement is the entire agreement on its subject. It replaces earlier agreements on that subject. Terms in your purchase orders do not apply.
31.10. Electronic acceptance and electronic records are valid and binding.
32. Contact
Hometown Workforce, LLC 2519 Provence Pl, Biloxi, MS 39531, USA legal@hometownworkforce.com