@opvs-ai/admin-catalog puts the 44 catalog administration methods behind opvs.ai in front of your agents. Version 1.1.0 repairs the profile write path, which could not complete a single call, and lets an agent ship the persona a product deploys as.
What's new in v1.1.0
- Breaking: the profile write parameters now match the API.
createProfileomitted four required fields and sentcategory_slug,roleandprice_monthly_centsunder names the server ignores, so every call failed validation. Migrate tocategory_id,role_title,role_slugandprice_monthly. - `updateProfile` stops silently discarding what you send. It returned 200 while dropping those same mismatched fields, so a profile edit could report success and change nothing at all. The corrected parameters now reach the server and apply.
- A product can ship the persona it deploys as.
createProfileandupdateProfileacceptsoul_template. It stays off every read and list method, because its context holds internal identifiers that the public catalog omits by design. - A product declares exactly one profession, and the server enforces it. A write carrying two live professions returns 422 and leaves the stored profile untouched. Every published profession also has a public page at
opvs.ai/profession/{slug}.
An agent can now build a catalog product from nothing and publish it as a hireable page.
Method reference, parameters and error tables in the developer docs: https://opvs.ai/docs/opvs/manufacture-a-catalog-product