Output Schema

[elisalimli]

Summary

Fixes #918

Depends on

#925

Test plan

Here's an example SAML that I tested to scrape structured data from Amazon.com

workflows:
  - superagent:
      llm: gpt-3.5-turbo-1106
      name: Browser assistant
      intro: 👋 Hi there! How can I help search for answers on the internet.
      tools:
        - scraper:
            name: browser
            use_for: searching the internet
            metadata:
              apiKey: 9EA0OH7T2LXAXHPV3K036MN192XQZ2DRMP2XA9QC0KF2LBU9XCMXK8CJREIU5AVNOYPMHJD4Y2AEF8NR
      prompt: Use the browser to answer any questions
      output_schema:
        type: array
        items:
          type: object
          required:
            - id
            - name
          properties:
            id:
              type: integer
            product_name:
              type: integer
            product_price:
              type: string

  "input": "i need product name, product price, store name from https://www.amazon.com/s?k=apple+m3&crid=2CSLNASAYI715&sprefix=apple+mc%2Caps%2C376&ref=nb_sb_noss_2",

[render]

Your Render PR Server URL is https://superagent-pr-922.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-co2t5gmd3nmc73cotsg0.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
superagent-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 30, 2024 5:57pm

[homanp]

Left a comment @elisalimli

[homanp]

@elisalimli this needs work with the REST API and SDKs as well. could you add that as well? On the workflow invoke function.

[elisalimli]

@elisalimli this needs work with the REST API and SDKs as well. could you add that as well? On the workflow invoke function.

@homanp it will work on the SDK too. We just call our existing api_endpoints in SAML. So whatever works there will work on REST API/SDK

[homanp]

@elisalimli this needs work with the REST API and SDKs as well. could you add that as well? On the workflow invoke function.

@homanp it will work on the SDK too. We just call our existing api_endpoints in SAML. So whatever works there will work on REST API/SDK

I don't see any outputSchema key work invoking workflows in the REST API.

[elisalimli]

@elisalimli this needs work with the REST API and SDKs as well. could you add that as well? On the workflow invoke function.

@homanp it will work on the SDK too. We just call our existing api_endpoints in SAML. So whatever works there will work on REST API/SDK

I don't see any outputSchema key work invoking workflows in the REST API.

Yes, we don't. I thought it's redundant to receive outputSchema every time. Instead we're storing in the database and read from there.

[homanp]

Remove

[homanp]